Rails code following 37signals conventions: REST purity, fat models, thin controllers, and clarity over cleverness.
Works with
Applies DHH style patterns including CRUD controllers, state-as-records instead of booleans, and Current attributes for defaults
Covers controllers, models, views, architecture, testing, and dependency decisions with specific naming conventions and code examples
Emphasizes vanilla Rails over gems: Minitest over RSpec, fixtures over factory_bot, Solid Queue over Sidekiq,
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondhh-rails-styleExecute the skills CLI command in your project's root directory to begin installation:
Fetches dhh-rails-style from everyinc/compound-engineering-plugin and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate dhh-rails-style. Access via /dhh-rails-style in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
1
total installs
1
this week
13.4K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
13.4K
stars
<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:
Development Philosophy:
Specify a number or describe your task.
| 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, cache | references/architecture.md |
| 5, test, testing, minitest, fixture | references/testing.md |
| 6, gem, dependency, library | references/gems.md |
| 7, review | Read all references, then review code |
| 8, general task | Read relevant references based on context |
After reading relevant references, apply patterns to the user's code.
<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)active, unassigned (business terms, not SQL-ish)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
# Symbol arrays with spaces inside brackets
before_action :set_message, only: %i[ show edit update destroy ]
# Private method indentation
private
def set_message
@message = Message.find(params[:id])
end
# Expression-less case for conditionals
case
when params[:before].present?
messages.page_before(params[:before])
else
messages.last_page
end
# Bang methods for fail-fast
@message = Message.create!(params)
# Ternaries for simple conditionals
@room.direct? ? @room.users : @message.mentionees
State as Records:
Card.joins(:closure) # closed cards
Card.where.missing(:closure) # open cards
Current Attributes:
belongs_to :creator, default: -> { Current.user }
Authorization on Models:
class User < ApplicationRecord
def can_administer?(message)
message.creator == self || admin?
end
end
</quick_reference>
<reference_index>
All detailed patterns in references/:
| File | Topics |
|---|---|
references/controllers.md |
REST mapping, concerns, Turbo responses, API patterns, HTTP caching |
references/models.md |
Concerns, state records, callbacks, scopes, POROs, authorization, broadcasting |
references/frontend.md |
Turbo Streams, Stimulus controllers, CSS layers, OKLCH colors, partials |
references/architecture.md |
Routing, authentication, jobs, Current attributes, caching, database patterns |
references/testing.md |
Minitest, fixtures, unit/integration/system tests, testing patterns |
references/gems.md |
What they use vs avoid, decision framework, Gemfile examples |
| </reference_index> |
<success_criteria> Code follows DHH style when:
Important Disclaimers:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
everyinc/compound-engineering-plugin
wshobson/agents
davila7/claude-code-templates
intellectronica/agent-skills
am-will/codex-skills
sickn33/antigravity-awesome-skills
Registry listing for dhh-rails-style matched our evaluation — installs cleanly and behaves as described in the markdown.
We added dhh-rails-style from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
dhh-rails-style reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend dhh-rails-style for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
dhh-rails-style fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend dhh-rails-style for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
dhh-rails-style reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added dhh-rails-style from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for dhh-rails-style matched our evaluation — installs cleanly and behaves as described in the markdown.
dhh-rails-style fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 48