What problem does it solve? Choosing the right tool in the non-Laravel PHP ecosystem is confusing: developers often reach for a full framework when a single standalone library would do, or confuse Symfony HttpFoundation with PSR-7. This Skill provides an orientation map that answers "which tool fits this problem, and where do I go next?" without pretending to be an implementation expert. ## Core Features & Use Cases - Ecosystem Routing: Decision tables map needs (CLI tool, micro-API, API-first product) to the right option — standalone Symfony components, API Platform 4.3, or Slim 4.15. - Standalone Component Guidance: Covers Composer-installable Symfony components (Console, Process, EventDispatcher, Validator, Serializer) usable without any framework. - Explicit Boundaries: Routes Laravel tasks to laravel-expert, PSR-7/15/17/18 work to php-http-psr, and flags that no deep Symfony full-stack expert exists instead of improvising. - Use Case: You need to build a small webhook receiver in PHP. The Skill's decision table routes you to Slim 4.15, notes the CVE-fixed 4.15.2 minimum version, and hands implementation specifics to the research-expert agent for verification. ## Quick Start Ask which PHP tool fits your project — for example, whether to use a Symfony component, API Platform, or Slim for a small API — and follow the routing recommendation.
