symfonyapi-platform-state-providers

MakFly's avatarfrom MakFly

Master API Platform State Providers and Processors to decouple data retrieval and persistence from entities, enabling clean architecture and custom data sources

⭐26stars🔀4forks📁View on GitHub🕐Updated Dec 30, 2025

When & Why to Use This Skill

This Claude skill specializes in implementing and optimizing Symfony API Platform State Providers and Processors. It assists developers in decoupling data retrieval and persistence logic from core entities, facilitating a clean architecture. By leveraging these components, the skill enables the integration of custom data sources and complex business logic, ensuring your API remains scalable, maintainable, and framework-agnostic where necessary.

Use Cases

  • Custom Data Sourcing: Implementing State Providers to fetch API resources from external microservices, NoSQL databases, or legacy systems rather than standard database entities.
  • Clean Architecture Refactoring: Decoupling business logic from the persistence layer by moving data handling into dedicated Processors and Providers to improve code testability.
  • Complex Persistence Workflows: Using State Processors to handle multi-step operations during resource creation or updates, such as triggering external webhooks, password hashing, or sending notifications.
  • DTO Integration: Facilitating the mapping between internal domain models and external API Data Transfer Objects (DTOs) to maintain a strict separation of concerns.
namesymfony:api-platform-state-providers
descriptionUse when symfony api platform state providers

symfony:api-platform-state-providers (Micro)

Use when

  • Use when symfony api platform state providers

Rules

  • Keep changes minimal and focused
  • Ask before running servers/builds/tests
  • Load reference/examples only on explicit request

References

  • reference.md
  • docs/complexity-tiers.md