SkillsAdd

smithery/MakFly

symfony:api-platform-resources

Configure API Platform v4 resources with explicit operations, pagination, and typed OpenAPI for clean, versioned REST/GraphQL APIs

Installation

$ npx skills add smithery/MakFly --skill symfonyapi-platform-resources
View on skills.sh ↗ Website ↗

Also in this package

Other skills from smithery/MakFly · top by installs.

npx skills add smithery/MakFly
symfony:writing-plans 0 symfony:using-symfony-superpowers 0 symfony:twig-components 0 symfony:test-doubles-mocking 0 symfony:tdd-with-phpunit 0 symfony:tdd-with-pest 0 symfony:symfony-scheduler 0 symfony:symfony-messenger 0 symfony:symfony-cache 0 symfony:runner-selection 0

Browse all from smithery/MakFly

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Write, Edit, Bash, Glob, Grep

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,255 B
  • docs SUMMARY.md 76 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Api Platform Resources (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