laravel-specialist
Skill0 starsChanged 3 months agoMITView on GitHub
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.
- Reads credentials
15 other projects use a version of this.
Adopted by
Most recently taken up by
- lamb92009/claude-skillstheir own version, first seen Nov 16, 2026
- santiago-migoni/claude-skillstheir own version, first seen Nov 8, 2026
- lsyamsiar/claude-skillstheir own version, first seen Nov 1, 2026
- codeApe-7/ai-agent-workflowGrouptheir own version, first seen Nov 1, 2026
- hu465/claude-skills-their own version, first seen Oct 25, 2026
- lgzarturo/codeconductortheir own version, first seen Oct 18, 2026
Used with
Projects with it also use ui-ux-pro-max.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
StrayDragonSkillui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Also in 6 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- Jeffallan/claude-skills★ 12ksame name
- jshsakura/awesome-opencode-skills★ 31same name
- codeApe-7/ai-agent-workflowGroup★ 18same name
- belokonm/claude-supercode-skills★ 11same name
- PIXARTSeu/Synapse★ 9same name
- thesaifalitai/claude-setup★ 9same name
- PUPT-Quantum-Leap/capstone-nlcom-volunteer-management-system★ 4same name
- zacklecon/claude-skills★ 3same name
- hu465/claude-skills-★ 0same name
- james-paul25/claude-skill★ 0same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- in-progress/AGENTS.mdAGENTS.md
- test-skills/AGENTS.mdAGENTS.md
- docx-processingSkill
- email-composerSkill
- fastapi-expertSkill
- fastapiSkill
- frontend-code-reviewSkill
- frontend-testingSkill
- laravel-boostSkill
- migrate-radix-to-baseSkill
- pdf-processingSkill
- php-specialistSkill
- python-proSkill
- react-expertSkill
- rust-engineerSkill
- seo-optimizerSkill
- shadcn-code-reviewSkill
- shadcnSkill
- tailwind-v4Skill
- tauri-developmentSkill
- tauri-v2Skill
- typescript-proSkill
- xlsx-processingSkill
- zustand-stateSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 12 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Check for Livewire, Inertia, or Blade-only frontend stack
- Very specific: line 35
[HARD-GATE]: When uncertain about any Laravel API — verify, don't guess.
- Distinctive: line 39
Verify directory structure follows Laravel conventions (see section below)
- Distinctive: line 43
Check caching strategy (config, route, view, application-level)
- Distinctive: line 49
Write migrations first — schema is the source of truth
- Distinctive: line 52
Create controllers (single-action or resourceful) bound to routes
- Distinctive: line 53
Add Form Requests for validation, Policies for authorization
- Very specific: line 107
Use {{ }} for escaped output, {!!
- Very specific: line 108
Prefer Blade directives (@auth, @can, @env) over raw PHP conditionals
- Distinctive: line 157
Use deferred providers for bindings that are not needed on every request
- Distinctive: line 158
Avoid heavy logic in providers — delegate to dedicated classes
- Distinctive: line 228
Do NOT skip migrations and edit the database directly -- migrations are the source of truth.
- Distinctive: line 229
Do NOT put business logic in controllers because "it's faster" -- use Action classes.
- Distinctive: line 230
Do NOT skip Form Requests because "the validation is simple" -- it always grows.
- Very specific: line 231
Do NOT disable preventLazyLoading() because "it's annoying" -- fix the N+1 queries.
- Distinctive: line 232
Do NOT store money as floats because "the amounts are small" -- precision errors compound.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
See REFERENCE.md for code examples.
Accessors, Mutators, and Casts
See REFERENCE.md for code examples.
Query Optimization with Eager Loading
See REFERENCE.md for code examples.
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
See REFERENCE.md for code examples.
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
See REFERENCE.md for code examples.
Event / Listener Pattern
See REFERENCE.md for code examples.
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+):
See REFERENCE.md for code examples.
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
See REFERENCE.md for code examples (Unit Test, Feature Test, Queue and Event Fakes, Browser Test).
Artisan Commands, Migrations, Seeders, Factories
Migration Conventions
See REFERENCE.md for code examples.
Factory Patterns
See REFERENCE.md for code examples.
Laravel Directory Structure Conventions
See REFERENCE.md for the full directory layout.
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

