Laravel 11 12 App Guidelines
Ship Laravel 11/12 features and bugfixes across API or full-stack apps while respecting AGENTS.md, detected stack, and Laravel Boost docs.
Overview
Laravel 11/12 App Guidelines is an agent skill for the Build phase that applies a stack-aware Laravel 11/12 workflow with docs-first repo rules and Laravel Boost guidance.
Install
npx skills add https://github.com/thienanblog/awesome-ai-agent-skills --skill laravel-11-12-app-guidelinesWhat is this skill?
- Reads AGENTS.md and docs/ before coding decisions
- Stack detection via composer.json, package.json, Docker, and config
- Supports Sail/Docker vs host commands, API-only vs Inertia/React/Livewire/Vue/Blade
- Laravel Boost search-docs first; Context7 fallback when Boost is unavailable
- Covers Fortify, Tailwind v4, Wayfinder, PHPUnit, Pint, and Boost MCP tooling
Adoption & trust: 784 installs on skills.sh; 61 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent is editing a Laravel 11/12 repo but keeps guessing the frontend stack, Docker vs host commands, and project conventions buried in AGENTS.md.
Who is it for?
Solo builders on Laravel 11 or 12 with mixed stacks (API, Inertia, Livewire) who already use or can enable Laravel Boost MCP tools.
Skip if: Greenfield projects without an existing Laravel app, Laravel 10-only codebases, or teams that forbid reading AGENTS.md and local docs before implementation.
When should I use this skill?
Implementing features, fixing bugs, or making UI/backend changes on Laravel 11 or 12 while following AGENTS.md and project docs.
What do I get? / Deliverables
After running the skill, the agent follows detected stack conventions, Boost-backed docs, and Laravel 11/12 structure for consistent feature and bugfix changes.
- Stack-aware Laravel changes aligned with repo conventions
- Commands run via Sail/Docker or host per detection
- Tests and formatting consistent with PHPUnit and Pint usage
Recommended Skills
Journey fit
Canonical shelf is build because the skill governs day-to-day Laravel implementation across backend and optional UI stacks. Backend subphase fits the core PHP/Laravel workflow; full-stack frontends are secondary variants detected from the repo.
How it compares
Use as a procedural Laravel workspace playbook instead of generic PHP snippets or one-off framework chat prompts.
Common Questions / FAQ
Who is laravel-11-12-app-guidelines for?
Solo and indie builders shipping Laravel 11 or 12 apps who want their coding agent to respect repo-specific AGENTS.md rules, optional Docker/Sail, and common full-stack variants.
When should I use laravel-11-12-app-guidelines?
Use it in the Build phase when implementing features, fixing bugs, or changing UI and backend together on Laravel 11/12, and during Ship prep when aligning tests (PHPUnit/Pint) with the detected stack.
Is laravel-11-12-app-guidelines safe to install?
Review the Security Audits panel on this Prism page and only grant MCP/filesystem access your repo policy allows; the skill expects reading project docs and running framework tooling.
SKILL.md
READMESKILL.md - Laravel 11 12 App Guidelines
# Laravel 11/12 App Guidelines ## Overview Apply a consistent workflow for Laravel 11/12 apps with optional frontend stacks, Dockerized commands, and Laravel Boost tooling. ## Quick Start - 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. ## Stack Detection - 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) ## Laravel 11/12 Core Conventions - 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. - Create Form Request classes for validation instead of inline validation. - Prefer named routes and `route()` for URL generation. - When altering columns, include all existing attributes in the migration to avoid dropping them. - Ask before destructive database operations (e.g., reset/rollback/fresh). ## API-Only Mode - Use `routes/api.php`; avoid Inertia and frontend assumptions. - Prefer API Resources and versioning if the repo already uses them. - Follow the repo's auth stack (Sanctum/Passport/custom) and response format conventions. - Do not require Vite/Tailwind/NPM unless the repo already includes them. ## Inertia + React + Wayfinder (if present) - Use `Inertia::render()` for server-side routing; place pages under `resources/js/Pages` unless the repo says otherwise. - Use `<Form>` or `useForm` for Inertia forms; add skeleton/empty states for deferred props. - Use `<Link>` or `router.visit()` for navigation. - Use Wayfinder named imports for tree-shaking; avoid default imports; regenerate routes after changes if required. ## Livewire / Vue / Blade (if present) - Follow existing component patterns and conventions; do not mix frameworks unless the repo already does. - Keep UI strings in the repo's expected language. ## Tailwind CSS v4 (if present) - Use `@import "tailwindcss";` and `@theme` for tokens. - Avoid deprecated utilities; use replacements (e.g., `shrink-*`, `grow-*`, `text-ellipsis`). - Use `gap-*` for spacing between items; follow existing dark mode conventions if present. ## Testing and Formatting - Use PHPUnit; generate tests with `php artisan make:test --phpunit` and prefer feature tests. - Run the minimal relevant tests (`php artisan test <file>` or `--filter=`). - Run `vendor/bin/pint --dirty` before finalizing code changes. - After minimal tests pass, offer to run the full test suite. ## Laravel Boost MCP Tools (when available) - `search-docs` before changing behavior or using framework features. - `list-artisan-commands` to confirm Artisan options. - `list-routes` to inspect routing changes. - `tinker` for PHP debugging and `database-query` for read-only DB checks. - `browser-logs` to inspect frontend errors. - `get-absolute-url` for sharing project URLs. - See `references/boost-tools.md` for query patterns and to