laravel-specialist
Use when building or maintaining Laravel applications — Eloquent ORM, Blade, Livewire, queues, Pest testing, middleware, service providers, migrations. Trigger conditions: Laravel project setup, Eloquent model design, Blade or Livewire component creation, queue/job implementation, Pest test writing, middleware configuration, migration authoring, route definition, Form Request validation, policy authorization, Sanctum/Passport authentication, Horizon queue monitoring.
- Installs
- 77
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/pixel-process-ug/superkit-agents --skill laravel-specialist- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads laravel-specialist automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Laravel Specialist
Overview
Design, build, and maintain production-grade Laravel applications following the framework's conventions and best practices. This skill covers the full Laravel ecosystem: Eloquent ORM with advanced relationship patterns, Blade templating and Livewire interactivity, queue and event systems, middleware pipelines, service providers, Pest testing at every layer, and Artisan tooling for migrations, seeders, and factories.
Apply this skill whenever Laravel is the application framework, whether greenfield or brownfield.
Multi-Phase Process
Phase 1: Context Discovery
- Identify Laravel version (
composer.json->laravel/framework) - Scan
config/for enabled packages and custom configuration - Map existing models, relationships, and migration history
- Review
routes/for API, web, console, and channel definitions - Catalog installed first-party packages (Sanctum, Horizon, Telescope, Pulse, Pennant, Scout, Cashier)
- Check for Livewire, Inertia, or Blade-only frontend stack
STOP — Do NOT begin architecture review without knowing the Laravel version and installed packages.
Documentation Verification Protocol
[HARD-GATE] When uncertain about any Laravel API — verify, don't guess. Use mcp__context7__resolve-library-id then mcp__context7__query-docs (preferred). Fallback: fetch from https://github.com/laravel/docs. For Livewire, Pest, Inertia — resolve each via context7 separately. Returned docs override memorized knowledge.
Phase 2: Architecture Review
- Verify directory structure follows Laravel conventions (see section below)
- Assess service provider registrations and deferred loading
- Review middleware stack ordering and grouping
- Evaluate queue connection configuration and worker topology
- Check caching strategy (config, route, view, application-level)
STOP — Do NOT begin implementation until architecture gaps are documented.
Phase 3: Implementation
- Write migrations first — schema is the source of truth
- Build Eloquent models with relationships, scopes, casts, and accessors
- Implement business logic in dedicated Action or Service classes
- Create controllers (single-action or resourceful) bound to routes
- Add Form Requests for validation, Policies for authorization
- Wire events, listeners, and jobs for asynchronous workflows
STOP — Do NOT skip Form Requests and Policies. Inline validation and authorization are anti-patterns.
Phase 4: Testing
- Unit tests for isolated logic (Actions, Value Objects, Casts)
- Feature tests for HTTP endpoints and middleware behavior
- Browser tests with Laravel Dusk for critical user flows
- Database assertions with
assertDatabaseHas,assertSoftDeleted - Queue and event fakes for side-effect verification
STOP — Do NOT proceed to optimization without passing tests at all layers.
Phase 5: Optimization
- Apply eager loading to eliminate N+1 queries
- Cache expensive computations and config/route/view
- Index frequently-queried columns; use
EXPLAINto verify - Profile with Telescope or Debugbar in development
- Configure Horizon for production queue monitoring
Eloquent Patterns
Relationships
| Relationship | Method | Inverse | Use Case |
|---|---|---|---|
| One-to-One | hasOne | belongsTo | User -> Profile |
| One-to-Many | hasMany | belongsTo | Post -> Comments |
| Many-to-Many | belongsToMany | belongsToMany | User <-> Roles (pivot) |
| Has-Many-Through | hasManyThrough | — | Country -> Posts (through Users) |
| Polymorphic | morphMany / morphTo | morphTo | Comments on Posts and Videos |
| Many-to-Many Polymorphic | morphToMany | morphedByMany | Tags on Posts and Videos |
Scopes
// Local scope — reusable query constraint
public function scopeActive(Builder $query): Builder
{
return $query->where('status', 'active');
}
// Usage: User::active()->where('role', 'admin')->get();
// Global scope — applied to all queries on the model
protected static function booted(): void
{
static::addGlobalScope('published', function (Builder $builder) {
$builder->whereNotNull('published_at');
});
}
Accessors, Mutators, and Casts
// Attribute accessor/mutator (Laravel 11+ syntax)
protected function fullName(): Attribute
{
return Attribute::make(
get: fn () => "{$this->first_name} {$this->last_name}",
);
}
// Custom cast
protected function casts(): array
{
return [
'options' => AsCollection::class,
'address' => AddressCast::class,
'status' => OrderStatus::class, // Backed enum
'metadata' => 'array',
'is_active' => 'boolean',
'amount' => MoneyCast::class,
];
}
Query Optimization with Eager Loading
// BAD — N+1 problem: 1 query for posts + N queries for authors
$posts = Post::all();
foreach ($posts as $post) {
echo $post->author->name; // Triggers lazy load each iteration
}
// GOOD — Eager load: 2 queries total
$posts = Post::with('author')->get();
// Nested eager loading
$posts = Post::with(['author', 'comments.user'])->get();
// Constrained eager loading
$posts = Post::with(['comments' => function ($query) {
$query->where('approved', true)->latest()->limit(5);
}])->get();
// Prevent lazy loading in development
Model::preventLazyLoading(! app()->isProduction());
Blade Templates and Livewire Components
Blade Conventions
- Layouts:
resources/views/layouts/app.blade.phpusing@yield/@sectionor component-based<x-app-layout> - Components:
resources/views/components/— anonymous or class-based - Partials:
@include('partials.sidebar')for reusable fragments - Use
{{ }}for escaped output,{!! !!}only when HTML is explicitly trusted - Prefer Blade directives (
@auth,@can,@env) over raw PHP conditionals
Livewire Patterns
// Full-page Livewire component (Livewire 3+)
#[Layout('layouts.app')]
#[Title('Dashboard')]
class Dashboard extends Component
{
public string $search = '';
#[Computed]
public function users(): LengthAwarePaginator
{
return User::where('name', 'like', "%{$this->search}%")->paginate(15);
}
public function render(): View
{
return view('livewire.dashboard');
}
}
Frontend Stack Decision Table
| Decision | Choose Livewire | Choose Inertia |
|---|---|---|
| Existing Blade codebase | Yes | No |
| SPA-like experience required | Partial (with wire:navigate) | Yes |
| Team has Vue/React expertise | No | Yes |
| Server-side rendering priority | Yes | Depends on adapter |
| Real-time reactivity | Yes (polling, streams) | Requires Echo setup |
| SEO-critical pages | Either works | Either works (SSR adapter) |
Queue, Job, and Event Patterns
Job Design
class ProcessInvoice implements ShouldQueue
{
use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;
public int $tries = 3;
public int $backoff = 60;
public int $timeout = 120;
public string $queue = 'invoices';
public function __construct(public readonly Invoice $invoice) {}
public function handle(PdfGenerator $generator): void
{
$generator->generate($this->invoice);
}
public function failed(Throwable $exception): void
{
// Notify admin, log to error tracker
}
}
Event / Listener Pattern
// Dispatch event
OrderPlaced::dispatch($order);
// Listener (queued)
class SendOrderConfirmation implements ShouldQueue
{
public function handle(OrderPlaced $event): void
{
Mail::to($event->order->user)->send(new OrderConfirmationMail($event->order));
}
}
Sync vs Async Decision Table
| Task | Queued | Synchronous |
|---|---|---|
| Sending emails / notifications | Yes | Never in request cycle |
| PDF generation | Yes | Only if < 2s and user waits |
| Payment processing | Depends — webhook-driven preferred | If gateway responds < 5s |
| Cache warming | Yes | Never |
| Audit logging | Yes (high-volume) or Sync (low-volume) | If guaranteed delivery needed |
| Search indexing | Yes | Never |
Middleware and Service Providers
Middleware Stack Ordering
Middleware order matters. The default stack in bootstrap/app.php (Laravel 11+):
->withMiddleware(function (Middleware $middleware) {
$middleware->web(append: [
HandleInertiaRequests::class, // After session, before response
]);
$middleware->api(prepend: [
EnsureFrontendRequestsAreStateful::class, // Sanctum SPA auth
]);
$middleware->alias([
'role' => EnsureUserHasRole::class,
'verified' => EnsureEmailIsVerified::class,
]);
})
Service Provider Best Practices
- Register bindings in
register(), never resolve from the container there - Boot logic (event listeners, route model binding, macros) goes in
boot() - Use deferred providers for bindings that are not needed on every request
- Avoid heavy logic in providers — delegate to dedicated classes
Testing with Pest
Unit Test
test('order total calculates tax correctly', function () {
$order = Order::factory()->make(['subtotal' => 10000, 'tax_rate' => 0.08]);
expect($order->total)->toBe(10800);
});
Feature Test
test('authenticated user can create a post', function () {
$user = User::factory()->create();
$response = $this->actingAs($user)
->postJson('/api/posts', [
'title' => 'My Post',
'body' => 'Content here.',
]);
$response->assertCreated()
->assertJsonPath('data.title', 'My Post');
$this->assertDatabaseHas('posts', [
'user_id' => $user->id,
'title' => 'My Post',
]);
});
Queue and Event Fakes
test('placing an order dispatches confirmation job', function () {
Queue::fake();
$order = Order::factory()->create();
PlaceOrder::dispatch($order);
Queue::assertPushed(SendOrderConfirmation::class, function ($job) use ($order) {
return $job->order->id === $order->id;
});
});
Browser Test (Dusk)
test('user can complete checkout flow', function () {
$this->browse(function (Browser $browser) {
$browser->loginAs(User::factory()->create())
->visit('/cart')
->press('Checkout')
->waitForText('Order Confirmed')
->assertSee('Thank you');
});
});
Artisan Commands, Migrations, Seeders, Factories
Migration Conventions
// Always include down() for rollback capability
public function up(): void
{
Schema::create('invoices', function (Blueprint $table) {
$table->id();
$table->foreignId('user_id')->constrained()->cascadeOnDelete();
$table->string('number')->unique();
$table->integer('amount'); // Store money as cents
$table->string('currency', 3);
$table->string('status')->default('draft');
$table->timestamp('due_at')->nullable();
$table->timestamps();
$table->softDeletes();
$table->index(['user_id', 'status']);
});
}
Factory Patterns
class InvoiceFactory extends Factory
{
public function definition(): array
{
return [
'user_id' => User::factory(),
'number' => $this->faker->unique()->numerify('INV-####'),
'amount' => $this->faker->numberBetween(1000, 100000),
'currency' => 'USD',
'status' => 'draft',
'due_at' => now()->addDays(30),
];
}
public function paid(): static
{
return $this->state(fn () => ['status' => 'paid']);
}
public function overdue(): static
{
return $this->state(fn () => [
'status' => 'sent',
'due_at' => now()->subDays(7),
]);
}
}
Laravel Directory Structure Conventions
app/
├── Actions/ # Single-purpose action classes
├── Casts/ # Custom Eloquent casts
├── Console/Commands/ # Artisan commands
├── Enums/ # PHP backed enums
├── Events/ # Event classes
├── Exceptions/ # Custom exception classes
├── Http/
│ ├── Controllers/ # Resourceful or single-action controllers
│ ├── Middleware/ # Request/response middleware
│ └── Requests/ # Form Request validation
├── Jobs/ # Queued job classes
├── Listeners/ # Event listener classes
├── Mail/ # Mailable classes
├── Models/ # Eloquent models
├── Notifications/ # Notification classes
├── Observers/ # Model observers
├── Policies/ # Authorization policies
├── Providers/ # Service providers
├── Rules/ # Custom validation rules
├── Services/ # Domain service classes
└── View/Components/ # Blade view components
database/
├── factories/ # Model factories
├── migrations/ # Schema migrations (timestamped)
└── seeders/ # Database seeders
resources/views/
├── components/ # Blade components
├── layouts/ # Layout templates
├── livewire/ # Livewire component views
└── mail/ # Email templates
routes/
├── api.php # API routes
├── channels.php # Broadcast channels
├── console.php # Artisan closures
└── web.php # Web routes
tests/
├── Feature/ # Feature (integration) tests
├── Unit/ # Unit tests
└── Browser/ # Dusk browser tests
Decision Tables
Authentication Strategy
| Scenario | Recommended Approach |
|---|---|
| SPA + same domain | Sanctum (cookie-based, CSRF) |
| SPA + different domain | Sanctum (token-based) |
| Mobile app | Sanctum (token-based) |
| Third-party API consumers | Passport (OAuth2) |
| Simple API tokens | Sanctum (plaintext hash) |
| Social login | Socialite + Sanctum |
Caching Layer
| Data Type | Cache Driver | TTL | Invalidation |
|---|---|---|---|
| Config / routes / views | File (artisan cache) | Until next deploy | artisan optimize:clear |
| Database query results | Redis / Memcached | 5-60 min | Event-driven or TTL |
| Full-page / fragment | Redis | 1-15 min | Cache tags |
| Session data | Redis | Session lifetime | Automatic |
| Rate limiting | Redis | Window duration | Automatic |
File Storage
| Scenario | Disk | Driver |
|---|---|---|
| User uploads (production) | s3 | Amazon S3 / compatible |
| User uploads (local dev) | local | Local filesystem |
| Public assets | public | Local with symlink |
| Temporary files | local | Local, pruned by schedule |
Anti-Patterns / Common Mistakes
| Anti-Pattern | Why It Fails | What To Do Instead |
|---|---|---|
| Fat controllers | Untestable, unmaintainable business logic | Move logic to Action or Service classes |
| Raw SQL in controllers | SQL injection risk, not portable | Use Eloquent or Query Builder |
| Missing mass-assignment protection | Data manipulation vulnerabilities | Always define $fillable or $guarded |
| Inline validation in controllers | Couples validation to HTTP layer | Use Form Requests |
| Jobs without retry/backoff config | Silent failures, no recovery | Configure $tries, $backoff, failed() |
| Over-using global scopes | Hidden query behavior surprises developers | Prefer local scopes |
| Storing money as floats | Floating-point precision errors | Use integer cents, convert at presentation |
| Missing database indexes | Slow queries at scale | Add composite indexes for WHERE + ORDER BY |
| Secrets in config files | Credential leaks in version control | Use .env exclusively |
| Testing against production DB | Data corruption, unreliable tests | Use SQLite in-memory or dedicated test DB |
| Lazy loading in API responses | N+1 queries, slow API responses | Enable preventLazyLoading() in dev |
Anti-Rationalization Guards
- Do NOT skip migrations and edit the database directly -- migrations are the source of truth.
- Do NOT put business logic in controllers because "it's faster" -- use Action classes.
- Do NOT skip Form Requests because "the validation is simple" -- it always grows.
- Do NOT disable
preventLazyLoading()because "it's annoying" -- fix the N+1 queries. - Do NOT store money as floats because "the amounts are small" -- precision errors compound.
Integration Points
| Skill | How It Connects |
|---|---|
php-specialist | Modern PHP 8.x patterns underpin all Laravel code |
laravel-boost | AI-assisted development guidelines and MCP tooling |
senior-backend | API design, caching strategies, event-driven architecture |
test-driven-development | Pest testing workflow with RED-GREEN-REFACTOR |
database-schema-design | Migration planning, indexing strategy, data modeling |
security-review | Sanctum/Passport configuration, CSRF, input validation |
performance-optimization | Query profiling, cache tuning, queue worker scaling |
deployment | Forge/Vapor/Envoyer deployment, artisan optimize |
context7 MCP | Fetches up-to-date Laravel docs when information is uncertain |
laravel/docs GitHub | Authoritative source for Laravel API reference |
Skill Type
FLEXIBLE — Adapt the multi-phase process to the scope of work. A single model change may skip Phase 2 entirely, while a new module should follow all five phases. Core conventions (eager loading, Form Requests, Pest tests, migration-first schema changes) are non-negotiable regardless of scope.
FAQ
What does the laravel-specialist skill do?
Use when building or maintaining Laravel applications — Eloquent ORM, Blade, Livewire, queues, Pest testing, middleware, service providers, migrations. Trigger conditions: Laravel project setup, Eloquent model design, Blade or Livewire component creation, queue/job implementation, Pest test writing, middleware configuration, migration authoring, route definition, Form Request validation, policy authorization, Sanctum/Passport authentication, Horizon queue monitoring.
How do I install laravel-specialist?
Run npx skills add https://github.com/pixel-process-ug/superkit-agents --skill laravel-specialist in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/laravel-specialist/ (personal) or .claude/skills/laravel-specialist/ (project).
Which AI agents can use laravel-specialist?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is laravel-specialist safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains laravel-specialist?
It is published by pixel-process-ug in pixel-process-ug/superkit-agents. It has 77 recorded installs.
More from pixel-process-ug/superkit-agents
ui-ux-pro-max
pixel-process-ug/superkit-agents
Use when the user needs full UI/UX design intelligence — styles, palettes, fonts, UX guidelines, chart selection, and accessible, performant implementation across any supported stack. Triggers: user says "design", "UI", "UX", "color palette", "typography", "accessibility", "responsive design", "chart type", "style guide", building any user-facing interface.
frontend-ui-design
pixel-process-ug/superkit-agents
Use when designing UI components, creating component architectures, implementing responsive layouts, setting up design systems, or selecting state management solutions for frontend applications
reverse-engineering-specs
pixel-process-ug/superkit-agents
Use when onboarding to an existing codebase that lacks specifications — exhaustively traces code paths and produces implementation-free behavioral specifications for safe refactoring, feature addition, or legacy modernization
canvas-design
pixel-process-ug/superkit-agents
Use when the user needs HTML Canvas, SVG graphics, data visualization, generative art, or interactive visual elements with D3.js or similar libraries. Triggers: user says "canvas", "SVG", "chart", "data visualization", "D3", "generative art", "animation", "interactive graphics", drawing on screen.
autonomous-loop
pixel-process-ug/superkit-agents
Use when running Ralph-style iterative autonomous development. Triggers on /ralph or /loop commands, when autonomous iterative development is needed, when a project has specs and an implementation plan ready for iterative execution, or when deterministic context loading with subagent delegation and dual-condition exit gates is required. Orchestrates PLANNING, BUILDING, and STATUS cycles.
mobile-design
pixel-process-ug/superkit-agents
Use when the user needs mobile app design and development patterns for React Native, Flutter, or SwiftUI — including platform HIG compliance, gestures, and offline-first architecture. Triggers: user says "mobile", "iOS", "Android", "React Native", "Flutter", "SwiftUI", "app design", "mobile navigation", "touch targets", "offline-first".
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.