Laravel architecture patterns, routing/controllers, Eloquent ORM, service layers, queues, events, caching, and API resources for production apps.
SkillScore91Maintained
Automatic
◆Coding pack
Last verified 8/22/2026
What it changes
Passed 20 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill91%
Checks it passed that the model alone missed
The Action class is declared as a final class.
The Form Request class defines a method named toDto.
Single-purpose use cases are placed under app/Actions.
and 4 more in the full report
5 fixed15 passed either way2 still failing0 broke
Pass-rate lift
+23 pp
Tokens
+84%
Agent turns
0%
Response time
-34%
Model gemini-3.6-flashMeasured 8/22/2026v620 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
I need to implement a subscription creation flow in my Laravel API. Could you write the Form Request class for validating input, an Action class to handle the subscription creation logic, and a Controller method that handles the HTTP request and returns a JSON response?
What was checked, without and with the skill
Checked
Without skill
With skill
The Action class is declared as a final class.
Missed
Passed
The Action method that processes the DTO is named handle.
Missed
Passed
The Form Request class defines a method named toDto.
Missed
Passed
case-01 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md416 linessingle file
Laravel Development Patterns
Production-grade Laravel architecture patterns for scalable, maintainable applications.
When to Use
Building Laravel web applications or APIs
Structuring controllers, services, and domain logic
Working with Eloquent models and relationships
Designing APIs with resources and pagination
Adding queues, events, caching, and background jobs
How It Works
Structure the app around clear boundaries (controllers -> services/actions -> models).
Use explicit bindings and scoped bindings to keep routing predictable; still enforce authorization for access control.
Favor typed models, casts, and scopes to keep domain logic consistent.
Keep IO-heavy work in queues and cache expensive reads.
Centralize config in config/* and keep environments explicit.
Examples
Project Structure
Use a conventional Laravel layout with clear layer boundaries (HTTP, services/actions, models).