Production Laravel Architecture

Transform business requirements into maintainable, production-ready Laravel applications. This skill enforces strict separation between HTTP, domain logic, and infrastructure—making business rules testable, configurable, and independent of framework details.

When to Apply

• Complex Workflows: Processes spanning multiple models or external APIs (checkouts, approvals, provisioning, imports)
• State Machines: Entities with strict lifecycle rules and guarded transitions (orders, documents, jobs, tasks)
• Policy Engines: Features with configurable rules, tiers, or permissions that change based on business strategy
• Financial Logic: Money handling, calculations, fee structures, or multi-party payments
• Notification Systems: Multi-channel, scheduled, or conditional user communications
• Refactoring: Moving from fat controllers or fat models to explicit service layers

Scope check: DDD overhead pays off at ~30+ use cases. For simpler apps, a well-structured MVC monolith is the right call. Don't architect past your complexity.

Requirements: PHP 8.0+ (uses match expressions and constructor property promotion). For PHP 7.4, replace match with switch and drop constructor promotion.