Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fbarrento/laravel-rules
Applies Francisco Barrento's Laravel, Pest, model, and naming conventions that override generic Laravel guidance.
Passed 14 of 18 test cases with the skill, and 2 of 18 without it.
and 24 more in the full report
14 fixed3 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Write a Pest feature test file verifying that an unauthenticated user cannot access the `/dashboard` route.
| Checked | Without skill | With skill |
|---|---|---|
| The response includes a 'Rules consulted:' header citing rules/testing/conventions.md prior to code. | Missed | Passed |
| The test file starts with declare(strict_types=1); | Missed | Passed |
The instructions your model reads when the skill loads.
This file is a ROUTER, not the rules. Reading it does NOT mean you have
"applied the skill." The actual rules live in rules/**/*.md and are NOT in
your context yet.
Before you write or edit ANY class you MUST, in order:
Rules consulted: <comma-separated relative paths of every rule file you read>
If that line would be empty, you are NOT ready to write code — return to
step 2.## Checklist section of each rule
file you used and confirm every item against your code. Report any item
you cannot satisfy instead of silently skipping it.Hard rules:
Higher priority than .agents/skills/laravel-best-practices when both
apply. Use Laravel and Pest documentation for API syntax; use these
files for project code shape.
The building-block vocabulary this skill reasons in — Action, Query, Service, Model, Data object, Value object, Enum, Exception, Job — is
test cases passed, vs 2 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.