---
name: Api Platform State Providers
slug: api-platform-state-providers
category: AI Engineering
description: Api Platform State Providers helps you design API Platform v4 state providers and processors to separate retrieval and persistence from entities. Use it when defining operation contracts, mapping DTOs, and enforcing validation and security behavior.
github: "https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/api-platform-state-providers"
language: TypeScript
stars: 208
forks: 20
install: "npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/api-platform-state-providers ~/.claude/skills/api-platform-state-providers"
installs_to: ~/.claude/skills/api-platform-state-providers
source_path: skills/api-platform-state-providers/SKILL.md
collection_size: 23
category_size: 2970
collection_url: "https://dirskills.com/collections/dev-toolings/superpowers-symfony"
added: 2026-09-04T05:27:04.298Z
last_synced: 2026-09-04T05:27:04.298Z
canonical_url: "https://dirskills.com/skills/api-platform-state-providers"
---

# Api Platform State Providers

Api Platform State Providers helps you design API Platform v4 state providers and processors to separate retrieval and persistence from entities. Use it when defining operation contracts, mapping DTOs, and enforcing validation and security behavior.

**Install:**

```bash
npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/api-platform-state-providers ~/.claude/skills/api-platform-state-providers
```

## README

# Api Platform State Providers (Symfony)

## Use when
- Designing or evolving API Platform contracts and operations.
- Aligning serialization, validation, and security behavior.

## Default workflow
1. Define operation-level contract and payload boundaries.
2. Implement resource/DTO/provider/processor changes with explicit mapping.
3. Apply operation-specific validation and security constraints.
4. Validate functional behavior across happy and negative paths.

## Guardrails
- Keep API contract explicit and version-aware.
- Avoid exposing internal entity fields implicitly.
- Prevent drift between docs and actual serialization.

## Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.

## Output contract
- API artifacts changed (resource/DTO/provider/processor).
- Contract/security decisions and rationale.
- Functional verification results.

## References
- `reference.md`
- `docs/complexity-tiers.md`