laravel

laravel

Core Laravel backend patterns organized around the six data-layer contract concerns: how relations are eager-loaded (no N+1, bulk writes), where untrusted input is validated, how deferred work is queued, how every query is scoped to the caller's tenant, who is allowed to act, and how tests stay fast and isolated. Target baseline is Laravel 12 / PHP 8.2 (a real modern Laravel 12 rework PoC). Deep mechanics live in references/; the body leads cleanly with the contract headings so a generic agent resolves each one by its verbatim string.

Pairs with: laravel-frontend for Blade / Livewire / Inertia template patterns. Load both on full-stack feature work (e.g. a controller that returns a Blade fragment on an HX-Request).

When to use

TRIGGER when: editing a Laravel project (composer.json + artisan, app/Models, app/Http/Controllers, app/Http/Requests, database/migrations/); adding an Eloquent model or relation; writing a controller, Form Request, or API Resource; dispatching a queued job; adding a Policy/Gate or tenant scope; running php artisan test; debugging N+1 or lazy-loading exceptions.

SKIP for: Blade/Livewire/Inertia template-only work (use laravel-frontend); non-Laravel PHP (raw PHP, Symfony, legacy ZF1 — different idioms); DevOps without code.

Pattern

Each ### below is a contract heading — the same verbatim string the active backend skill exposes on every stack, so a stack-agnostic agent greps one anchor and resolves the Laravel rule under it. Each carries a mechanism, the best-practice default to enforce, the anti-pattern to flag, and a runnable sample; depth pushes into references/.

ORM eager-loading

Eloquent lazy-loads relations on access, so any relation touched inside a loop without a prior with() is an N+1 storm. Eager-load every looped relation; use withCount() for counts, load()/loadMissing() to top-up an already-fetched model, chunkById()/lazy()/cursor() for large sets, and insert()/upsert() for bulk writes instead of create() in a loop.