37signals-rails

Provide Ruby on Rails coding principles and conventions from 37signals.

193|17|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/pproenca/dot-skills --skill 37signals-rails
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 37signals-rails
Source: https://github.com/pproenca/dot-skills/tree/main/skills/.experimental/37signals-rails
Command: npx skills add https://github.com/pproenca/dot-skills --skill 37signals-rails

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to the specific coding principles and conventions favored by 37signals for Ruby on Rails development, ensuring consistency and adherence to their established philosophy.

Core Features & Use Cases

  • Architectural Guidance: Understand the rationale behind choices like rich domain models over service objects and vanilla Rails over excessive gems.
  • Convention Enforcement: Learn specific rules for controllers, domain modeling, state management, and testing.
  • Use Case: When writing new Rails code or reviewing existing code, use this Skill to ensure it aligns with the 37signals approach, promoting maintainability and developer efficiency.

Quick Start

Apply the 37signals-rails skill to refactor the provided controller to use rich domain models instead of service objects.

Frequently Asked Questions about 37signals-rails

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

FAQPage Schema
How do I apply 37signals Rails conventions to my domain models?

37signals Rails conventions favor rich domain models over service objects, pushing business logic into the model itself. This approach minimizes excessive gem usage and keeps your application vanilla, promoting maintainability and developer efficiency.

What is the 37signals philosophy on Rails controller design?

The 37signals philosophy for Rails controller design emphasizes strict conventions and lean controllers. It provides specific rules derived from official sources and practical codebase examples to ensure consistency, state management, and architectural alignment.

Should I use service objects or rich models in Ruby on Rails?

You should use rich models instead of service objects in Ruby on Rails according to 37signals conventions. This architectural fundamental encourages vanilla Rails development over excessive gems, ensuring logic stays within the domain model.

How do I refactor a Rails controller to follow 37signals conventions?

To refactor a Rails controller following 37signals conventions, apply the skill to move logic from service objects into rich domain models. This ensures your code aligns with their established coding principles, state management, and testing methodologies.

Does the 37signals Rails approach require specific gems or dependencies?

The 37signals Rails approach does not require specific gems or dependencies; it advocates for vanilla Rails over excessive gem usage. Conventions cover database practices, frontend integration, and testing without adding external architectural dependencies.