About this skill

Problem Being Solved

PHP projects often suffer not from missing frameworks, but from weak typing, missing static analysis gates, and unclear async boundaries. Untyped callbacks, cross-layer payloads, and mixed routing/service boundaries can make Laravel or Symfony applications repeatedly expose risk during refactors, tests, and security review. This skill targets PHP 8.3 work and requires implementations to be organized around declare(strict_types=1), PHPStan level 9, Swoole, and PSR standards, so quality constraints appear in code and configuration rather than review prose.

How It Works and Boundaries

The skill proceeds by confirming the framework and PHP version, designing layers, routing, and service boundaries, implementing strictly typed code, checking PHPStan, typing, and security, then emitting a PhpAppSpec artifact. It accepts natural-language requirements, constraints, or optional code snippets, and can also consume an existing PhpAppSpec for second-pass optimization. Output includes the structured artifact plus a natural-language summary highlighting the 2-3 highest-priority fixes. It fits Laravel, Symfony, or native PHP 8.3 projects, and is not intended for PHP 5 legacy projects or non-PHP stacks.

Screenshots

Use Cases

Add strict typing to Laravel routes and service layers, then enforce PHPStan level 9 in CI.
Refactor Symfony controllers into service boundaries and emit a PhpAppSpec for security review.
Redesign a blocking PHP service with Swoole while checking types and concurrency boundaries.
Take an existing PhpAppSpec and optimize strict_types plus PHPStan configuration.

Best For

Backend engineers maintaining Laravel apps who need strict typing and PHPStan level 9 gates.
Engineers building Symfony enterprise services who need clear controller, service, and routing boundaries.
Platform engineers modernizing PHP async workloads who need Swoole concurrency and type-safety review.
Tech leads taking over PHP apps who need PhpAppSpec-based quality and security handoffs.