What problem does it solve?
This Skill captures production-ready Laravel architecture patterns so developers avoid bloated controllers, mixed responsibilities, and fragile event, queue, and cache handling while keeping the application structure predictable.
Core Features & Use Cases
- Layered structure: Keep controllers thin by routing through services and single-purpose actions, then return Api resources that match your DTO contracts.
- Routing clarity: Prefer resource controllers with scoped route-model bindings, nested routes that match parent-child relationships, and explicit bindings to prevent cross-tenant leaks.
- Model discipline: Apply typed casts, enums, query objects, scopes, and transactions alongside soft deletes or global scopes to keep Eloquent logic consistent and efficient.
- Operational hardening: Register service container bindings, centralize configuration, use form requests for validation, design migrations with timestamps and anonymous classes, and emit cached events plus queued jobs for IO-heavy work.
Quick Start
Ask the laravel-patterns skill to review your Laravel project structure and recommend controller, service, Eloquent, routing, caching, and queue conventions for production workloads.