laravel-11-12-app-guidelines

Structured workflow for Laravel 11/12 apps with stack detection, Docker support, and framework-specific conventions. Apply a consistent workflow for Laravel 11/12 apps with optional frontend stacks, Dockerized commands, and Laravel Boost tooling. - Detects and adapts to your stack: API-only, Inertia + React, Livewire, Vue, or Blade; Docker Compose/Sail or host commands - Enforces Laravel 11/12 conventions: bootstrap configuration, Eloquent models, Form Requests, named routes, and safe migrations - Integrates Laravel Boost MCP tools for docs search, Artisan commands, routing inspection, and database queries - Prioritizes repository instructions (AGENTS.md, docs/) and existing patterns over generic assumptions - Includes testing and formatting guidance: PHPUnit feature tests, Pint linting, and minimal test runs before full suite execution - 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...