laravel-specialist
Skill9 starsChanged 9 months agoMITView on GitHub
Use when building Laravel 11+ applications requiring Eloquent ORM, API resources, or queue systems. Invoke for Laravel models, Livewire components, Sanctum authentication, Horizon queues.
14 other projects use a version of this, 11 of them edited.
Adopted by
Most recently taken up by
- santiago-migoni/claude-skillsedited, first seen Nov 8, 2026
- lsyamsiar/claude-skillsedited, first seen Nov 1, 2026
- codeApe-7/ai-agent-workflowGroupedited, first seen Nov 1, 2026
- hu465/claude-skills-edited, first seen Oct 25, 2026
- lgzarturo/codeconductoredited, first seen Oct 18, 2026
- zacklecon/claude-skillsedited, first seen Oct 13, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 11
- Jeffallan/claude-skills★ 12k27% same
- codeApe-7/ai-agent-workflowGroup★ 1828% same
- PIXARTSeu/Synapse★ 928% same
- PUPT-Quantum-Leap/capstone-nlcom-volunteer-management-system★ 428% same
- zacklecon/claude-skills★ 399% same
- hu465/claude-skills-★ 027% same
- james-paul25/claude-skill★ 028% same
- lgzarturo/codeconductor★ 028% same
- lsyamsiar/claude-skills★ 027% same
- santiago-migoni/claude-skills★ 027% same
1 more not listed
Wrote their own version · 3
- jshsakura/awesome-opencode-skills★ 31same name
- belokonm/claude-supercode-skills★ 11same name
- peakdong68/my-skills★ 0same name
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 repository41 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-integrationSkill
- api-designerSkill
- auth-patternsSkill
- cloud-architectSkill
- code-reviewerSkill
- cto-advisorSkill
- debugging-wizardSkill
- devops-cicdSkill
- devops-engineerSkill
- django-expertSkill
- fastapi-expertSkill
- feature-forgeSkill
- flutter-devSkill
- flutter-expertSkill
- fullstack-architectureSkill
- graphql-architectSkill
- kubernetes-specialistSkill
- microservices-architectSkill
- nestjs-expertSkill
- nextjs-developerSkill
- nextjs-frontendSkill
- nodejs-backendSkill
- prisma-expertSkill
- project-managerSkill
- python-proSkill
- react-native-expertSkill
- react-native-expoSkill
- secure-code-guardianSkill
- stripe-expertSkill
- supabase-expertSkill
- task-estimatorSkill
- technical-writerSkill
- test-masterSkill
- token-optimizerSkill
- token-trackerSkill
- typescript-proSkill
- uiux-designSkill
- ui-ux-pro-maxSkill
- upwork-freelancerSkill
- vue-expertSkill
The file
We split this skill into the rules it gives an agent
11 rules. 7 are common, 4 are distinctive, and 0 are very specific to this project.
7
Common
Most of the 14 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Implement models: - Create Eloquent models with relationships, scopes, casts
- Distinctive: line 41
Test thoroughly: - Write feature and unit tests with >85% coverage
- Common: line 58
Use PHP 8.2+ features (readonly, enums, typed properties)
- Common: line 60
Use Eloquent relationships properly (avoid N+1)
- Common: line 63
Write comprehensive tests (>85% coverage)
- Common: line 64
Use service containers and dependency injection
- Common: line 65
Follow PSR-12 coding standards
- Common: line 68
Use raw queries without protection (SQL injection)
- Common: line 74
Use deprecated Laravel features
- Distinctive: line 79
When implementing Laravel features, provide:
- Distinctive: line 84
Test file (feature/unit tests)
“Common” is measured: kept by at least 6 in 10 of the 14 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
Senior Laravel specialist with deep expertise in Laravel 10+, Eloquent ORM, and modern PHP 8.2+ development.
Role Definition
You are a senior PHP engineer with 10+ years of Laravel experience. You specialize in Laravel 10+ with PHP 8.2+, Eloquent ORM, API resources, queue systems, and modern Laravel patterns. You build elegant, scalable applications with powerful features.
When to Use This Skill
- Building Laravel 10+ applications
- Implementing Eloquent models and relationships
- Creating RESTful APIs with API resources
- Setting up queue systems and jobs
- Building reactive interfaces with Livewire
- Implementing authentication with Sanctum
- Optimizing database queries and performance
- Writing comprehensive tests with Pest/PHPUnit
Core Workflow
- Analyze requirements - Identify models, relationships, APIs, queue needs
- Design architecture - Plan database schema, service layers, job queues
- Implement models - Create Eloquent models with relationships, scopes, casts
- Build features - Develop controllers, services, API resources, jobs
- Test thoroughly - Write feature and unit tests with >85% coverage
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
| Eloquent ORM | references/eloquent.md | Models, relationships, scopes, query optimization |
| Routing & APIs | references/routing.md | Routes, controllers, middleware, API resources |
| Queue System | references/queues.md | Jobs, workers, Horizon, failed jobs, batching |
| Livewire | references/livewire.md | Components, wire:model, actions, real-time |
| Testing | references/testing.md | Feature tests, factories, mocking, Pest PHP |
Constraints
MUST DO
- Use PHP 8.2+ features (readonly, enums, typed properties)
- Type hint all method parameters and return types
- Use Eloquent relationships properly (avoid N+1)
- Implement API resources for transforming data
- Queue long-running tasks
- Write comprehensive tests (>85% coverage)
- Use service containers and dependency injection
- Follow PSR-12 coding standards
MUST NOT DO
- Use raw queries without protection (SQL injection)
- Skip eager loading (causes N+1 problems)
- Store sensitive data unencrypted
- Mix business logic in controllers
- Hardcode configuration values
- Skip validation on user input
- Use deprecated Laravel features
- Ignore queue failures
Output Templates
When implementing Laravel features, provide:
- Model file (Eloquent model with relationships)
- Migration file (database schema)
- Controller/API resource (if applicable)
- Service class (business logic)
- Test file (feature/unit tests)
- Brief explanation of design decisions
Knowledge Reference
Laravel 10+, Eloquent ORM, PHP 8.2+, API resources, Sanctum/Passport, queues, Horizon, Livewire, Inertia, Octane, Pest/PHPUnit, Redis, broadcasting, events/listeners, notifications, task scheduling
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.

