What problem does it solve? Laravel applications fail in predictable ways that generic PHP knowledge misses: N+1 queries hidden in Blade loops, queue jobs duplicated by a misconfigured retry_after, dispatches racing ahead of uncommitted transactions, and Pennant flags silently reading as off in jobs. This Skill encodes the framework-specific rules, version differences, and silent-failure modes needed to build, review, debug, and upgrade Laravel 12/13 applications correctly. ## Core Features & Use Cases - Eloquent and data access rules: eager loading strategy, chaperone() for inverse N+1s, preventLazyLoading, mass-assignment discipline, migration staging, and index design. - Queue, event, and scheduling correctness: retry_after versus timeout, idempotency versus ShouldBeUnique, afterCommit dispatching, failed() instance semantics, and scheduler lock behavior. - HTTP, validation, and authorization: form requests, policies and gates, PreventRequestForgery in Laravel 13, rate limiting, and outbound HTTP timeout discipline. - Testing with Pest: deterministic fakes, freezeTime/travelTo, assertion strength, and suite-speed tuning. - Use Case: A controller issues hundreds of queries per request and a warehouse sync job duplicates shipments after deploy. The Skill pinpoints the N+1 and mass-assignment holes in the controller, the retry_after/timeout race in the queue config, and the transaction-dispatch hazard, with exact fixes. ## Quick Start Ask the agent to review your Laravel controller, model, and queue job for N+1 queries, mass-assignment risks, and queue misconfiguration, and propose concrete fixes.