Write Ruby and Rails code in DHH's distinctive 37signals style. Use this skill when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.
Inherits all available tools
Additional assets for this skill
This skill inherits all available tools. When active, it can use any tool Claude has access to.
references/architecture.mdreferences/controllers.mdreferences/frontend.mdreferences/gems.mdreferences/models.md<essential_principles>
"The best code is the code you don't write. The second best is the code that's obviously correct."
Vanilla Rails is plenty:
What they deliberately avoid:
Specify a number or describe your task. </intake>
<routing> | Response | Reference to Read | |----------|-------------------| | 1, "controller" | references/controllers.md | | 2, "model" | references/models.md | | 3, "view", "frontend", "turbo", "stimulus", "css" | references/frontend.md | | 4, "architecture", "routing", "auth", "job" | references/architecture.md | | 5, "review" | Read all references, then review code | | 6, general task | Read relevant references based on context |After reading relevant references, apply patterns to the user's code. </routing>
<quick_reference>
Verbs: card.close, card.gild, board.publish (not set_style methods)
Predicates: card.closed?, card.golden? (derived from presence of related record)
Concerns: Adjectives describing capability (Closeable, Publishable, Watchable)
Controllers: Nouns matching resources (Cards::ClosuresController)
Scopes:
chronologically, reverse_chronologically, alphabetically, latestpreloaded (standard eager loading name)indexed_by, sorted_by (parameterized)Instead of custom actions, create new resources:
POST /cards/:id/close → POST /cards/:id/closure
DELETE /cards/:id/close → DELETE /cards/:id/closure
POST /cards/:id/archive → POST /cards/:id/archival
</quick_reference>
<reference_index>
All detailed patterns in references/:
| File | Topics |
|---|---|
| controllers.md | REST mapping, concerns, Turbo responses, API patterns |
| models.md | Concerns, state records, callbacks, scopes, POROs |
| frontend.md | Turbo, Stimulus, CSS architecture, view patterns |
| architecture.md | Routing, auth, jobs, caching, multi-tenancy, config |
| gems.md | What they use vs avoid, and why |
| </reference_index> |
<success_criteria> Code follows DHH style when: