skills/laravel/laravel-tooling/SKILL.md
Configure Laravel ecosystem with custom Artisan commands, Vite asset bundling, Pint code styling, and Horizon queue monitoring. Use when creating Artisan commands, migrating from Mix to Vite, or configuring Pint code standards.
npx skillsauth add hoangnguyen0403/agent-skills-standard laravel-toolingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
composer require laravel/pint --dev; run ./vendor/bin/pint.vite.config.js with Laravel plugin; add @vite() in Blade layout.php artisan make:command SendNewsletters.composer require laravel/horizon; configure supervisors.See implementation examples for Artisan command pattern and project structure.
php artisan make:command SendNewsletters.protected $signature = 'newsletters:send {--queue}'.handle(): int. Commands auto-discovered in app/Console/Commands/.bootstrap/app.php (formerly Kernel).npm install and configure vite.config.js with Laravel plugin.@vite(['resources/css/app.css', 'resources/js/app.js'])) to your layout.npm run dev for local HMR and npm run build for production. No manual versioning needed.composer require laravel/pint --dev../vendor/bin/pint to apply preset: 'laravel' configuration from pint.json.composer require laravel/horizon. Run php artisan horizon:install and configure supervisors in config/horizon.php.HorizonServiceProvider. Access via /horizon in browser.resources/js../vendor/bin/pint before merging.development
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
development
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
development
Implements a strict Red-Green-Refactor loop to ensure zero production code is written without a prior failing test. Use when: creating new features, fixing bugs, or expanding test coverage.
testing
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.