Laravel 11/12 App Guidelines

Work from what the repository actually installs. Laravel 11 and 12 applications vary widely in skeleton, frontend, auth, and command runner, and most mistakes come from assuming a fresh-application default the project does not use.

Delegation

Run in the main conversation by default. Delegation can increase usage: obtain explicit approval for the proposed agent count and scope before using subagents. Reuse that approval within its bounds; ask again before expanding the approved count or scope.

Detect before deciding

Read repository instructions and the relevant documentation owners, then confirm from composer.json, composer.lock, package.json, frontend lockfiles, bootstrap/app.php, Compose files, and config/:

• the command path: host PHP, Sail, Docker Compose, or a repository wrapper, used consistently;
• API-only or full-stack, and the frontend: Inertia with React, Vue, or Svelte; Livewire; or Blade;
• the auth stack (Fortify, Sanctum, Passport, or custom) and the test runner (Pest or PHPUnit).

For version-sensitive behavior, use Laravel Boost search-docs when Boost is available, since it filters by installed versions; otherwise use the official documentation for the installed major. boost-tools.md covers Boost usage and its data-safety limits.

Follow the repository's architecture, naming, UI language, and component patterns, and keep its dependencies unless the user asks for a change.