
Laravel 11 12 App Guidelines
A structured workflow for Laravel 11/12 projects that detects your stack (API-only, Inertia+React, Livewire, Blade) and adjusts accordingly. It enforces reading AGENTS.md and docs/ first, uses Laravel Boost MCP tools for searching framework docs and inspecting routes, and follows modern Laravel conventions like bootstrap/app.php configuration and Form Requests over inline validation. The Tailwind v4 and Wayfinder guidance is helpful if you're using those. Honestly most valuable for the stack detection logic and the discipline of checking repo conventions before making assumptions. Runs Pint on dirty files and asks before destructive migrations, which saves cleanup time.
- skills.sh installs
- 980
- GitHub stars
- 69
- last updated
- Aug 21, 2026
Install
$ npx -y skills add thienanblog/awesome-ai-agent-skills --skill laravel-11-12-app-guidelines --agent claude-codeInstalls into .claude/skills of the current project.
Files
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).
Sponsors