Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
makfly avatar

Symfony:api Platform Filters Skill

  • 427 installs
  • 190 repo stars
  • Updated August 6, 2026
  • makfly/superpowers-symfony

Add and tune API Platform collection filters for search, ordering, and scoped queries when building Symfony REST list endpoints with predictable client query params.

About

Symfony API Platform filters skill guides implementation of SearchFilter, OrderFilter, and related API Platform filter types in Symfony backends. It helps teams expose safe, documented query parameters for list endpoints without hand-rolling repetitive repository filtering logic.

  • SearchFilter setup
  • OrderFilter configuration
  • scoped collection queries
  • query param conventions
  • API Platform filter services

Symfony:Api Platform Filters by the numbers

  • 427 all-time installs (skills.sh)
  • Ranked #19 of 68 PHP & Laravel skills by installs in the Skillselion catalog
  • Data as of Aug 11, 2026 (Skillselion catalog sync)
npx skills add https://github.com/makfly/superpowers-symfony --skill symfonyapi-platform-filters

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs427
repo stars190
Last updatedAugust 6, 2026
Repositorymakfly/superpowers-symfony

What it does

Add and tune API Platform collection filters for search, ordering, and scoped queries when building Symfony REST list endpoints with predictable client query params.

Files

SKILL.mdMarkdownGitHub ↗

Api Platform Filters (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. 2. Apply operation-specific validation and security constraints. 2. 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

Related skills

PHP & Laravelbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.