Does this skill support modern JavaScript frameworks like React?

No, it strictly adheres to the DHH preference for Hotwire (Turbo/Stimulus) and standard Rails partials to keep the frontend simple and integrated with the backend.

What is the core philosophy of the DHH Rails Style skill?

It follows the Omakase philosophy: utilizing vanilla Rails features and database-backed solutions (like Solid Queue) instead of reaching for external dependencies or complex abstractions like service objects.

Why does it suggest creating new controllers for simple actions?

To maintain REST purity, the skill suggests mapping actions like 'archive' to a specific 'ArchivalsController' (POST/DELETE) rather than adding custom non-CRUD methods to a primary controller.

How does this skill handle state management in models?

It encourages using records as state instead of boolean columns (e.g., using a 'Closures' table instead of a 'closed' boolean), allowing for better auditing and historical data tracking.

DHH Rails Style

Name: DHH Rails Style
Author: Folly-Partners

byFolly-Partners

API 개발

Applies the opinionated 37signals and DHH Omakase patterns to Ruby on Rails development.

소개

This skill transforms Claude into a domain expert on the distinctive Ruby and Rails patterns pioneered by DHH and the 37signals team. It enforces 'Vanilla Rails' principles, prioritizing RESTful resource mapping over custom controller actions, database-backed state management over external services like Redis, and the classic fat model, thin controller philosophy. By leveraging patterns extracted from production codebases like Fizzy and Campfire, it guides developers in creating lean, maintainable applications using Hotwire and Stimulus while intentionally avoiding heavy dependencies like Devise, Sidekiq, or complex service objects.

주요 기능

Replaces boolean state columns with rich, auditable database records
0 GitHub stars
Enforces RESTful resource mapping by converting custom actions into nested resources
Guides the implementation of 'clarity over cleverness' using Minitest and fixtures
Promotes horizontal code sharing through the use of Active Support Concerns
Prioritizes database-backed solutions like Solid Queue and Solid Cache over Redis

사용 사례

Designing a modern Rails application architecture using the Hotwire/Turbo stack
Refactoring complex service objects back into rich domain models and concerns
Conducting code reviews to ensure alignment with 37signals production standards

소개

주요 기능

Replaces boolean state columns with rich, auditable database records
0 GitHub stars
Enforces RESTful resource mapping by converting custom actions into nested resources
Guides the implementation of 'clarity over cleverness' using Minitest and fixtures
Promotes horizontal code sharing through the use of Active Support Concerns
Prioritizes database-backed solutions like Solid Queue and Solid Cache over Redis

사용 사례

Designing a modern Rails application architecture using the Hotwire/Turbo stack
Refactoring complex service objects back into rich domain models and concerns
Conducting code reviews to ensure alignment with 37signals production standards