laravel-11-12-app-guidelines

Apply a consistent workflow for Laravel 11/12 apps with optional frontend stacks, Dockerized commands, and Laravel Boost tooling. - Read repository instructions first: AGENTS.md . If docs/ exists, read docs/README.md and relevant module docs before decisions. - Detect the stack and command locations; do not guess. - Use Laravel Boost search-docs for Laravel ecosystem guidance; use Context7 only if Boost docs are unavailable. - Follow repo conventions for naming, UI language, docs-first policies, and existing component patterns. - Check composer.json , package.json , docker-compose.* , and config/* to confirm: - Docker Compose/Sail vs host commands - API-only vs full-stack - Frontend framework (Inertia/React, Livewire, Vue, Blade) - Auth (Fortify, Sanctum, Passport, custom) - Use the Laravel 11/12 structure: configure middleware, exceptions, and routes in bootstrap/app.php ; service providers in bootstrap/providers.php ; console configuration in routes/console.php . - Use Eloquent models and relationships first; avoid raw queries and DB:: unless truly necessary.