Skip to content

ericrisco/rsc-harness / skills/laravel

laravel

Verified

Use 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`).

FileKindSize
SKILL.mdskill md13.8 KB
evals/README.mdmarkdown764 B
evals/cases.yamlconfig3.2 KB
references/eloquent-patterns.mdmarkdown4.8 KB
references/queues-and-scheduling.mdmarkdown5.4 KB
scripts/verify.shexecutablescript4.9 KB

evals/cases.yaml

View on GitHub
skill: laravel

should_trigger:
  - prompt: "Add a queued job to send order confirmation emails with retries and backoff."
    why: "Core queues — ShouldQueue + $tries/backoff is the center of this skill."
  - prompt: "Create an Eloquent model and migration for posts with a many-to-many tags relationship."
    why: "Core Eloquent — models, migrations, belongsToMany are the framework surface this skill owns."
  - prompt: "Write a Pest feature test for the checkout endpoint with RefreshDatabase."
    why: "In-framework Pest feature testing — explicitly this skill's testing section."
  - prompt: "My job runs immediately during tests instead of going to the queue — how do I assert it was dispatched?"
    why: "Non-obvious: the sync-driver gotcha. No 'Laravel' keyword, but it is exactly Queue::fake/assertPushed territory."
  - prompt: "Where did app/Http/Kernel.php go? I can't find it to register my middleware."
    why: "Non-obvious orientation trigger — the L11/12 slim skeleton moved middleware to bootstrap/app.php."
  - prompt: "Configura una cua amb Horizon i Redis per processar pagaments."
    why: "Catalan phrasing for Redis+Horizon queue setup — queues are this skill's core."
  - prompt: "Crea una migración con relaciones para una tabla de pedidos."
    why: "Spanish phrasing for an Eloquent migration with relationships — core Eloquent."

should_not_trigger:
  - prompt: "Write a strict-typed PHP value object with readonly props and set up PHPStan at max level."
    route_to: php
    why: "Language/toolchain work (types, readonly, PHPStan) with no framework surface — the php skill."
  - prompt: "Design the REST contract: versioning, status codes, and pagination shape for our public API."
    route_to: api-design
    why: "Transport-agnostic contract design discipline, not implementing an API in Laravel."
  - prompt: "Do an OWASP threat-model and security review of our auth flow across the whole stack."
    route_to: security-audit
    why: "Cross-stack appsec discipline; Laravel keeps only framework-native guards."
  - prompt: "Set up Playwright browser E2E tests for the signup funnel."
    route_to: testing-web
    why: "Browser/E2E strategy, not in-framework Pest feature tests."
  - prompt: "Tune the indexes and slow-query plan for this MySQL database."
    route_to: mysql
    why: "DB engine schema/index tuning; Laravel covers Eloquent + queue config, not server tuning."

capability:
  - scenario: "Implement order processing: a ProcessOrder queued job with retries, a StoreOrderRequest Form Request doing validation and authorization, and a Pest feature test that asserts the job was dispatched (not executed). Target Laravel 11/12."
    must_include:
      - "a job implementing ShouldQueue with $tries and a backoff (method or property)"
      - "a Form Request with both authorize() and rules()"
      - "$fillable allowlist on the model (never protected $guarded = [])"
      - "Queue::fake() with Queue::assertPushed() to assert dispatch rather than side effects"
      - "RefreshDatabase in the Pest test"
      - "L11/12 awareness: config in bootstrap/app.php / schedule in routes/console.php, no app/Http/Kernel.php or app/Console/Kernel.php"
      - "no pre-11 idioms (no editing Kernel.php, no legacy $casts array where casts() is meant)"
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall