Skills
.Work. You
Rest

rails-37-style-philosophy-what-they-avoid

Community

37signals' tech choices and why.

Software Engineering#architecture#best practices#rails#development philosophy#gems#37signals
AuthorChwistophe
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This Skill clarifies the specific technologies, gems, and patterns that the 37signals development philosophy deliberately avoids, helping developers understand their rationale and make informed decisions about their own tech stacks.

Core Features & Use Cases

  • Technology Stacks: Details alternatives to popular gems like Devise, Pundit, RSpec, and FactoryBot.
  • Architectural Patterns: Explains the preference for rich domain models over service objects and form objects.
  • Frontend/Backend Choices: Outlines the use of Turbo/Stimulus over SPAs and Solid Queue over Sidekiq.
  • Use Case: A developer evaluating different authorization strategies can consult this skill to understand why 37signals prefers model predicates over gems like Pundit or CanCanCan.

Quick Start

Explain why 37signals avoids Devise for authentication.

Dependency Matrix

Required Modules

None required

Components

references

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: rails-37-style-philosophy-what-they-avoid
Download link: https://github.com/Chwistophe/agent-skills-unofficial-37-signals-rails-way-fizzy/archive/main.zip#rails-37-style-philosophy-what-they-avoid

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.