laravel-expert — Claude Code skill: senior Laravel engineering

What laravel-expert does

The skill sets a role. The agent replies as a Senior Laravel Engineer, follows current framework standards and leaves legacy patterns alone unless you ask for them. Inside is a rule set covering architecture, routing, validation, Eloquent, API design, authentication, queues, caching and Blade. Business logic goes to services, validation to FormRequest classes, API output to Resources, authorization to Policies and Gates.

There is a separate list of anti-patterns: fat controllers, logic in routes, oversized service classes, blind mass assignment, hardcoded config values, duplicated logic across controllers. When writing code the skill asks for complete examples with namespace declarations, strict typing and return types. When reviewing, it wants structural problems named first, then Laravel-native fixes with the tradeoffs spelled out. Feature design follows a fixed outline: architecture overview, file structure, implementation, explanation, possible improvements.

The scope is Laravel 10/11+, so on an older project the advice may not match what your composer.json pins — worth checking the version before you accept the diff. The skill also tells the agent to prefer framework-native solutions over third-party packages, skip needless abstractions and not assume cloud infrastructure.