laravel-enterprise

What problem does it solve?

Many Laravel projects grow with fat controllers, inconsistent validation, and ad-hoc data access that make teamwork, testing, and maintenance difficult; this Skill prescribes a clear layered architecture to avoid those pitfalls and enable predictable, team-scale development.

Core Features & Use Cases

• Layered Architecture: Enforces Request → FormRequest → Controller → Service → Repository → Eloquent to keep controllers thin and responsibilities separated.
• Enterprise Patterns: Promotes Repository interfaces with bindings, service layer orchestration with transactions and side effects, DTOs between layers, API Resources for consistent responses, and centralized exception handling.
• Use Case: Ideal when building or refactoring an Orders API for a multi-developer backend where validation, transactional integrity, and predictable response shaping are required.

Quick Start

Create a new Laravel module for orders using repository interfaces, a service layer with transactions, FormRequests for validation, DTOs between layers, and API Resources for responses.