What problem does it solve?
It solves the problem of PHP codebases degrading into loosely typed, framework-entangled “big ball of mud” systems that are hard to test, maintain, and evolve.
Core Features & Use Cases
- Strict, type-driven PHP foundations: Enforces strict types, native typing, immutability for DTO/value objects, and enums for finite sets.
- Clean architecture guidance for frameworks: Keeps domain logic framework-free, pushes infrastructure concerns (Eloquent/Doctrine, HTTP/queues) to the edges, and clarifies dependency direction.
- Production-grade engineering practices: Covers error handling, persistence patterns, performance concerns (e.g., avoiding N+1), and robust testing/testing boundaries.
- Use Case: Refactor a Laravel or Symfony application into domain/application/infrastructure layers with DTOs, repository interfaces, and predictable exception handling so changes become safer and tests become meaningful.
Quick Start
Ask the skill to propose a strict-typed directory and layering plan for your current PHP project, including how to separate domain, application, and infrastructure while enforcing error-handling and testing boundaries.