dhh-rails-style

Enforce 37signals Rails conventions for Ruby code generation and review.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/hemory/amp --skill dhh-rails-style-hemory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dhh-rails-style
Source: https://github.com/hemory/amp/tree/main/.claude/plugins/compound-engineering/skills/dhh-rails-style
Command: npx skills add https://github.com/hemory/amp --skill dhh-rails-style-hemory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers write Ruby and Rails code that adheres to the distinctive, pragmatic, and efficient style championed by David Heinemeier Hansson (DHH) and used at 37signals.

Core Features & Use Cases

  • Convention Enforcement: Guides users on preferred Rails patterns, avoiding common "heavy" gems in favor of simpler, built-in solutions.
  • Code Review: Helps review existing code against DHH's principles for clarity, maintainability, and performance.
  • Use Case: When building a new Rails feature, consult this Skill to ensure your models are "fat," controllers are "thin," and you're leveraging Turbo and Stimulus effectively for frontend interactions.

Quick Start

Apply DHH's Rails conventions to the provided Ruby code snippet.

Frequently Asked Questions about dhh-rails-style

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce DHH Rails conventions when refactoring Ruby code?

To enforce DHH Rails conventions, apply 37signals patterns prioritizing REST purity, fat models, thin controllers, and clarity over cleverness during Ruby code generation and review.

What are DHH's best practices for structuring Rails models and controllers?

DHH's Rails best practices dictate keeping models fat with domain logic, controllers thin, and utilizing Current attributes for global request context to maintain clean architecture.

Does DHH's Rails coding style use Hotwire for frontend interactions?

Yes, DHH's Rails coding style leverages Hotwire patterns, specifically Turbo and Stimulus, for frontend interactions instead of building heavy single-page JavaScript applications.

What is the best way to review Ruby code against 37signals coding style?

The best way to review Ruby code against 37signals style is checking for REST purity, avoiding heavy gems in favor of built-in solutions, and ensuring clarity over cleverness.

When should I use Current attributes in Rails instead of traditional patterns?

Use Current attributes in Rails when you need to encapsulate global, per-request context like the current user, replacing traditional threading globals with a cleaner built-in approach.