> laravel-tooling
Manage 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. (triggers: package.json, composer.json, vite.config.js, artisan, vite, horizon, pint, blade)
curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/laravel-tooling?format=md"Laravel Tooling
Priority: P2 (MEDIUM)
Workflow: Set Up Development Tooling
- Install Pint —
composer require laravel/pint --dev; run./vendor/bin/pint. - Configure Vite — Set up
vite.config.jswith Laravel plugin; add@vite()in Blade layout. - Create custom command —
php artisan make:command SendNewsletters. - Add Horizon —
composer require laravel/horizon; configure supervisors.
Custom Artisan Command Example
See implementation examples for Artisan command pattern and project structure.
Implementation Guidelines
Artisan Commands
- Customization: Use
php artisan make:command SendNewsletters. - Definitions: Define
protected $signature = 'newsletters:send {--queue}'. - Execution: Implement
handle(): int. Commands are auto-discovered inapp/Console/Commands/. - Scheduling: Schedule in
bootstrap/app.php(formerly Kernel).
Asset Management (Vite)
- Scaffolding: Run
npm installand configurevite.config.jswith the Laravel plugin. - Blade Integration: Add the @vite directive (
@vite(['resources/css/app.css', 'resources/js/app.js'])) to your layout. - Migration: Use Vite (not Mix) — replace mix() with vite() in Blade templates and remove laravel-mix.
- Workflow: Run
npm run devfor local HMR andnpm run build for production. No manual versioning needed.
Code Quality & Monitoring
- Pint Styling: Enforce standards with
composer require laravel/pint --dev. - Usage: Run
./vendor/bin/pintto apply thepreset: 'laravel'configuration frompint.json. - Queue Observability: Use
composer require laravel/horizon. Runphp artisan horizon:installand configure supervisors inconfig/horizon.php. - Horizon Security: Set authentication gates in
HorizonServiceProvider. Access via/horizonin browser.
Anti-Patterns
- No Laravel Mix: Migrate to Vite for faster HMR.
- No JS in Blade templates: Move scripts to
resources/js. - No manual DB edits: Use Artisan commands or migrations.
- No unstyled commits: Run
./vendor/bin/pintbefore merging.
References
> related_skills --same-repo
> common-store-changelog
Generate user-facing release notes for the Apple App Store and Google Play Store by collecting git history, triaging user-impacting changes, and drafting store-compliant changelogs. Enforces character limits (App Store ≤4000, Google Play ≤500), tone, and bullet format. Use when generating release notes, app store changelog, play store release, what's new, or version release notes for any mobile app. (triggers: generate changelog, app store notes, play store release, what's new, release notes, ve
> golang-tooling
Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code. (triggers: gopls, golangci-lint, golangci.yml, go vet, goimports, staticcheck, go tooling, go lint)
> common-ui-design
Design distinctive, production-grade frontend UI with bold aesthetic choices. Use when building web components, pages, interfaces, dashboards, or applications in any framework (React, Next.js, Angular, Vue, HTML/CSS). (triggers: build a page, create a component, design a dashboard, landing page, UI for, build a layout, make it look good, improve the design, build UI, create interface, design screen)
> common-owasp
OWASP Top 10 audit checklist for Web Applications (2021) and APIs (2023). Load during any security review, PR review, or codebase audit touching web, mobile backend, or API code. (triggers: security review, OWASP, broken access control, IDOR, BOLA, injection, broken auth, API review, authorization, access control)