Agent skill · thienanblog
laravel-13-app-guidelines
Coordinator-routed implementation and upgrade guidance for confirmed Laravel 13 repositories or Laravel 12-to-13 upgrades when framework conventions materially own the work. Use after project-development-mindset inspects the installed or target laravel/framework major, or directly when explicitly invoked or installed standalone. Never load both Laravel version skills; do not use merely for supporting Docker, test, frontend, or Artisan commands.
What it needs
About 6k tokens when loaded.
What this skill does
Laravel 13 App Guidelines Overview Use a repository-first workflow for Laravel 13 work. Detect the actual framework, packages, frontend, command runner, and local conventions before selecting a Laravel pattern; do not turn optional Laravel 13 capabilities into dependencies. This skill owns version-specific Laravel implementation and upgrade 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 agent count and scope after being told that delegation can increase usage. Ask again before expanding the approved scope. Execute the Workflow 1. Read repository instructions such as AGENTS.md, CLAUDE.md, and relevant docs/ files before making decisions. 2. Inspect composer.json, composer.lock, package.json, frontend lockfiles, bootstrap/app.php, bootstrap/providers.php, routes, configuration, and tests. Use php artisan about or composer show when dependencies are installed and the repository's command runner permits it. 3. Identify the supported command path: host PHP, Sail, Docker Compose, or a repository wrapper. Reuse that path consistently and do not assume Sail. 4. Confirm the application shape: API-only or full-stack; Blade, Livewire, or Inertia; frontend framework and major version; authentication; test runner; queue, cache, search, and database drivers. 5. Consult version-matched guidance before changing framework behavior. Prefer Laravel Boost search-docs when Boost is installed and available; otherwise use Laravel 13.x or the installed package's official documentation. 6. Follow existing architecture and naming. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thienanblog/laravel-13-app-guidelines