Agent skill · software engineering · thienanblog

laravel-11-12-app-guidelines

Coordinator-routed implementation guidance for confirmed Laravel 11 or 12 repositories when framework conventions materially own the work. Use after project-development-mindset inspects laravel/framework, or directly when explicitly invoked or installed standalone. Never load both Laravel version skills; Laravel 12-to-13 upgrades use the Laravel 13 skill. Do not use merely for supporting Sail, Docker, test, or frontend commands.

Why this skill is useful

Provides specific guidelines and workflows for Laravel 11/12 applications, including stack detection and project conventions that the AI wouldn't reliably generate on its own.

What it needs

Requires docker installed locally. About 3k tokens when loaded. Last updated 2026-08-05. 63 stars on the source repository.

What this skill does

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. This skill owns version-specific Laravel implementation guidance, not the whole task lifecycle. Keep routine testing, documentation, Docker command execution, and UI reuse as supporting work. Return routing control to project-development-mindset if debugging, test strategy, local container topology, UI concept work, or deployment becomes the primary concern. Run this skill in the main conversation. Do not spawn subagents, agent teams, or delegated parallel workers unless the user explicitly approves the proposed count and scope after being told that doing so can increase usage. Ask again before expanding an approved scope. Quick Start Read repository instructions first: AGENTS.md. If docs/ exists, read docs/README.md and relevant module docs before decisions. Detect installed versions, the stack, and command locations; do not guess. Use Laravel Boost search-docs for version-matched ecosystem guidance; use official versioned Laravel or package documentation if Boost is unavailable. Follow repo conventions for naming, UI language, docs-first policies, and existing component patterns. Stack Detection Check composer.json, composer.lock, package.json, frontend lockfiles, bootstrap/app.php, docker-compose., and config/ to confirm: Docker Compose/Sail vs host commands API-only vs full-stack Frontend framework (Inertia with React, Vue, or Svelte; Livewire; Blade) Auth (Fortify, Sanctum, Passport, custom) Laravel 11/12 Core Conventions When the application uses the modern Laravel 11/12 skeleton, configure middleware, exceptions, and routes in bootstrap/app.php; register service providers in bootstrap/providers.php; define closure commands and schedules in routes/console.php. Preserve a supported upgraded structure unless the task requires reorganizing it. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills thienanblog/laravel-11-12-app-guidelines

View the source on GitHub

Browse the @skills marketplace