dhh-rails-style

Apply DHH Rails conventions to controllers, models, and views.

50|14|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill dhh-rails-style-all-the-vibes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dhh-rails-style
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/dhh-rails-style
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill dhh-rails-style-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Rails teams often face inconsistent conventions, resulting in tangled controllers, bloated logic, and maintenance headaches. This skill codifies DHH/37signals Rails style to promote REST-first design, domain-rich models, and clear, maintainable Rails code.

Core Features & Use Cases

  • Apply 37signals/DHH Rails conventions to Ruby and Rails code across controllers, models, and views.
  • Provide a reference-driven framework to guide code reviews, refactors, and onboarding.
  • Support for using concerns, state-as-records patterns, Minitest with fixtures, and Turbo/Stimulus-driven UIs in Rails apps.

Quick Start

Install the skill and start applying DHH Rails conventions to your models, controllers, and views.

Frequently Asked Questions about dhh-rails-style

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

FAQPage Schema
How do I apply DHH Rails conventions to my Ruby codebase?

You can enforce DHH Rails conventions for consistent controllers, models, and views by applying this skill's reference-driven framework to refactoring, scaffolding, and code review workflows.

What is the best way to structure Rails controllers following 37signals style?

The best way to structure Rails controllers following 37signals style is to enforce REST-centric design patterns that keep controllers readable and push domain logic into rich models.

How does the state-as-records pattern work in Rails models?

The state-as-records pattern in Rails models persists state directly as database records rather than state machines, promoting domain-rich models and clear data integrity within your application.

Does this Rails style guide support Turbo and Stimulus for frontend development?

Yes, this Rails style guide supports Turbo and Stimulus-driven frontends, enforcing conventions that align with 37signals development patterns for interactive UIs.

Can I use Minitest with fixtures instead of RSpec when following DHH coding conventions?

Yes, you can use Minitest with fixtures when following DHH coding conventions, as this skill explicitly enforces Minitest and fixtures over alternative testing frameworks for Rails applications.

When should I use Rails concerns for horizontal behavior?

You should use Rails concerns for horizontal behavior when you need to extract shared logic across multiple models or controllers, following the 37signals convention of keeping domain logic clean and maintainable.