Laravel Specialist guides Claude through Laravel work in five steps: analyze requirements, design the schema and queues, implement models, build controllers, resources and jobs, and test. A table of checkpoints pairs each stage with an artisan command and the result it should give, such as migrate:status, route:list, queue:work —once, test with coverage and Pint.
Five reference files cover Eloquent, routing and API resources, queues, Livewire and testing.
What You Get
- Eloquent models with relationships, scopes, casts and soft deletes, plus migrations
- Controllers, form requests and API resources with route and versioning patterns
- Queued jobs with retries, backoff, chaining, batching, rate limits and Horizon setup
- Livewire components with validation, loading states and browser events
- Pest or PHPUnit feature and unit tests with factories and fakes, aimed at 85 percent coverage
Common Use Cases
- Creating models, migrations and factories for a new Laravel feature
- Building a JSON API with API resources and form request validation
- Moving slow work to queues and monitoring it with Horizon
- Adding a reactive Livewire form
- Fixing N+1 queries in Eloquent code
- Writing Pest tests for authenticated API routes
What Makes It Unique
A validation table ties each workflow stage to an artisan command and the output to expect, and the constraints ask for strict types, enums, service containers and tested queue failures. The skill names Sanctum authentication and Horizon alongside Eloquent, Livewire and testing, so one skill spans the usual Laravel feature set.
Under The Hood
The skill is a SKILL.md with five reference files and no scripts, and the references load by topic. The workflow tells the agent to run php artisan make:model, migrate:status, route:list, queue:work and test, and the Pint linter, so it uses the shell and writes PHP source, migrations and tests. Migrations change the project database when run. The queue reference shows storage settings that read AWS credentials from environment variables, and the testing reference fakes outgoing HTTP calls. The skill does not tell the agent to browse the web.