ce-dhh-rails-style

Apply 37signals/DHH Rails conventions to Ruby and Rails code.

2|Updated Apr 30, 2026

Search Tags:#conventions #ruby #rails #coding-style #dhh #37signals

Ready to run

npx skills add https://github.com/thisisryanswift/zellij-agent-tools --skill ce-dhh-rails-style

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce-dhh-rails-style
Source: https://github.com/thisisryanswift/zellij-agent-tools/tree/main/.opencode/skills/ce-dhh-rails-style
Command: npx skills add https://github.com/thisisryanswift/zellij-agent-tools --skill ce-dhh-rails-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines Ruby on Rails development by enforcing the 37signals/DHH conventions across codebases, improving consistency, readability, and onboarding for teams that want a clearly defined style.

Core Features & Use Cases

Pattern enforcement across controllers, models, and views to promote RESTful resources and conventional Rails design.
State-as-records approach with concerns like Closeable, Watchable, and Eventable patterns to track changes over time.
Turbo/Stimulus alignment to maximize server-rendered interactivity with minimal custom JavaScript.
Code-review guidance and refactoring discipline focused on DHH/37signals principles, enabling faster, safer iterations.

Quick Start

Describe your Rails task in plain language and I will apply the DHH style to generate pattern-compliant changes.

Frequently Asked Questions about ce-dhh-rails-style

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

FAQPage Schema

How do I apply DHH Rails style to my Ruby on Rails codebase?▼

To apply DHH Rails style, you describe your Rails task in plain language to enforce 37signals conventions. This generates pattern-compliant changes across controllers, models, and views, emphasizing RESTful design, minimal service objects, and simple authorization for readability.

What are the 37signals conventions for Rails controllers and models?▼

37signals conventions for Rails controllers and models prioritize RESTful resources, minimal service objects, and state-as-records. This approach uses concerns like Closeable, Watchable, and Eventable to track changes over time, ensuring high maintainability and conventional design.

Does DHH Rails style work with Turbo and Stimulus patterns?▼

Yes, DHH Rails style directly aligns with Turbo and Stimulus patterns. It maximizes server-rendered interactivity with minimal custom JavaScript, ensuring your frontend architecture follows 37signals conventions for faster and safer iterations.

What is the best way to refactor Rails code to use state-as-records?▼

The best way to refactor Rails code to use state-as-records is applying concerns like Closeable, Watchable, and Eventable. This 37signals pattern tracks changes over time directly within models rather than extracting logic into external service objects.

Can I use DHH Rails conventions for code review and refactoring?▼

Yes, you can use DHH Rails conventions for code review and refactoring. It provides guidance focused on 37signals principles, enabling faster and safer iterations while enforcing readability and maintainability across your Ruby on Rails codebase.

When should I avoid using service objects in Ruby on Rails?▼

You should avoid using service objects in Ruby on Rails when following DHH conventions, which favor minimal service objects. Instead, logic should remain within conventional RESTful controllers, state-as-records models, and concerns to maintain readability.