- Home
- Skills
- Makfly
- Superpowers Symfony
- Api Platform Security
api-platform-security_skill
- Shell
69
GitHub Stars
2
Bundled Files
3 weeks ago
Catalog Refreshed
2 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill makfly/superpowers-symfony --skill api-platform-security- reference.md8.1 KB
- SKILL.md1.2 KB
Overview
This skill delivers robust API Platform contracts in Symfony with explicit operations, mapping, and policy-safe behavior. It helps you define operation-level boundaries, implement DTOs/providers/processors, and align serialization, validation, and security. The goal is predictable, version-aware APIs that avoid accidental exposure of internal entity fields.
How this skill works
The skill inspects your resource definitions and operation configurations, then suggests explicit contracts and payload mappings. It identifies gaps between serialization groups, validation rules, and security expressions, and recommends code-level changes to providers, processors, or DTOs. Finally, it produces a concise output contract listing artifacts changed, security decisions, and functional verification results.
When to use it
- Designing or evolving API Platform resources and operations
- Aligning serialization groups, validation, and security expressions
- Preventing implicit exposure of internal entity fields
- Preparing a version-aware contract for client integration
- Auditing API behavior across happy and negative paths
Best practices
- Define operation-level DTOs to decouple API payloads from entities
- Keep contracts explicit and track version changes in the API spec
- Apply validation and security rules at the operation level, not only at the entity
- Map providers and processors clearly so behavior is predictable
- Run functional checks for both permitted and denied access scenarios
Example use cases
- Creating a PATCH operation with a dedicated DTO and processor to restrict writable fields
- Migrating an entity-backed resource to use read-only DTOs for responses
- Auditing a collection endpoint for leaked internal fields through serializer groups
- Implementing operation-specific security expressions that differ between GET and POST
- Documenting contract decisions for a breaking change prior to a new API version
FAQ
You will receive a list of API artifacts changed (resources/DTOs/providers/processors), the security and contract decisions with rationale, and functional verification results for key paths.
Does it modify entities directly?
No. The recommended approach is to introduce DTOs, explicit mappings, or providers/processors rather than exposing or modifying internal entity fields directly.