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.testing
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
documentation
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
development
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
data-ai
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.