ericrisco/rsc-harness / skills/rails
rails
VerifiedUse when building or maintaining a Ruby on Rails app — models, controllers, views, routes and migrations; ActiveRecord associations, scopes and query performance; Hotwire (Turbo and Stimulus) UI; Active Job or Solid Queue background work; and Rails tests. Covers N+1 queries, migration safety on live tables, and flaky system tests around Turbo Frames. NOT plain Ruby scripts, gems or CLIs with no Rails loaded (that is `ruby`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.1 KB |
| evals/README.md | markdown | 811 B |
| evals/cases.yaml | config | 2.8 KB |
| references/activerecord.md | markdown | 4.2 KB |
| references/hotwire.md | markdown | 4.0 KB |
| references/testing.md | markdown | 3.4 KB |
| scripts/verify.shexecutable | script | 4.4 KB |
evals/README.md
View on GitHub# Evals — rails
`cases.yaml` is a routing/trigger fixture, not an automated test harness. Run it by
hand (or via your router-eval tool): feed each `should_trigger` prompt to the skill
router and confirm it selects `rails`; feed each `should_not_trigger` prompt and confirm
it routes to the named sibling (`ruby`, `laravel`, `postgresdb`, `deployment`) instead.
For the `capability` case, give the scenario to the agent with this skill loaded and
check the produced Rails code satisfies every line in `must_include` — resourceful
routes, an association + validation, strong params, `includes`-based eager loading, a
Turbo Stream/morph live update, an `ApplicationSystemTestCase` test with auto-waiting
assertions, and Solid Queue (never Sidekiq) for any async. No external services or
network are required.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |