What problem does it solve? Laravel codebases built on a BaseController/BaseRepo architecture accumulate subtle runtime failures — LSP-violating overrides, dead FormRequest authorization, mass-assignment gaps, and version-incompatible validation APIs — that static analysis and php -l never catch. This Skill codifies the rules and production incident lessons needed to write and review Laravel controllers, repositories, migrations, and routes correctly. ## Core Features & Use Cases - Architecture Enforcement: Rules for BaseController/BaseRepo CRUD patterns, including parameter contravariance pitfalls, private method visibility, and mass-assignment gating via model $fillable. - Exception Handling & Security: Patterns for separating user-facing messages from logged debug details, safe trace logging, and correct HTTP status codes per exception type. - Migration & Route Safety: BigInt key conventions, PostgreSQL CHECK constraint handling, chunked data migrations, and route parameter constraints. - Use Case: When refactoring a Laravel controller that overrides BaseController::store(), apply the Skill to avoid narrowing Request to a FormRequest subtype, resolve the FormRequest via app(), and verify the override by actually loading the class rather than trusting php -l. ## Quick Start Ask the agent to review or write a Laravel controller, repository, migration, or route file using these best practices before committing the change.
