ericrisco/rsc-harness / skills/laravel
laravel
VerifiedUse when building or extending a Laravel 11/12 app — Eloquent models, migrations and relationships, routing with controllers and Form Requests, queues and background jobs, framework-native security (validation, mass-assignment, policies, signed URLs, rate limiting), and Pest/PHPUnit feature tests. NOT pure PHP language or toolchain work (that is `php`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.8 KB |
| evals/README.md | markdown | 764 B |
| evals/cases.yaml | config | 3.2 KB |
| references/eloquent-patterns.md | markdown | 4.8 KB |
| references/queues-and-scheduling.md | markdown | 5.4 KB |
| scripts/verify.shexecutable | script | 4.9 KB |
evals/README.md
View on GitHub# Evals: laravel
`cases.yaml` is read by the skills harness/eval runner, not an automated PHP test suite.
`should_trigger` and `should_not_trigger` gauge whether the SKILL.md `description` routes
correctly — a model reading only the frontmatter should fire on the trigger prompts (including
the non-obvious "where did Kernel.php go" and "my job runs inline in tests" cases and the
Spanish/Catalan phrasings) and defer the negatives to the named sibling (`php`, `api-design`,
`security-audit`, `testing-web`, `mysql`). The single `capability` case gauges body coverage:
run the scenario and check the response against the `must_include` rubric by hand. Nothing here
spins up Laravel or runs Pest — that is what `scripts/verify.sh` does against a real project.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |