skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
pproenca/dot-skills319 installs

37signals-rails

37signals Rails coding principles and conventions from DHH, Jorge Manrubia, and the Fizzy/Basecamp/HEY codebase. This skill should be used when writing, reviewing, or refactoring Ruby on Rails code following the 37signals philosophy — vanilla Rails, CRUD controllers, rich domain models, concerns, no service objects, Hotwire, Turbo, Stimulus, Solid Queue, Solid Cache, Solid Cable, multi-tenancy, Minitest, custom auth, or DHH conventions.

How do I install this agent skill?

npx skills add https://github.com/pproenca/dot-skills --skill 37signals-rails
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides architectural and coding guidelines for Ruby on Rails applications following the 37signals philosophy. It contains educational content and code examples to guide an AI agent in writing idiomatic Rails code. No security issues were detected.

  • Socketwarn

    2 alerts: gptAnomaly

  • Snykpass

    Risk: LOW · No issues

  • Runlayerwarn

    15/60 files flagged

What does this agent skill do?

37signals Rails Best Practices

Comprehensive coding principles and conventions for Ruby on Rails applications, as practiced at 37signals (Basecamp, HEY, Fizzy). Contains 56 rules across 8 categories, prioritized by architectural impact. Derived from official 37signals sources: the Fizzy codebase, STYLE.md, AGENTS.md, the Rails Doctrine, DHH's "On Writing Software Well" series, and the unofficial 37signals style guide (265 Fizzy PRs).

When to Apply

Reference these guidelines when:

  • Writing new Rails controllers, models, or views
  • Deciding between gems and vanilla Rails
  • Modeling state and database schema
  • Setting up background jobs, caching, or real-time features
  • Reviewing code for 37signals-style conventions
  • Refactoring toward rich domain models
  • Choosing authentication or authorization approach
  • Adding Stimulus controllers or Turbo patterns

Rule Categories by Priority

PriorityCategoryImpactPrefix
1Architecture FundamentalsCRITICALarch-
2Controllers & RESTCRITICALctrl-
3Domain ModelingHIGHmodel-
4State ManagementHIGHstate-
5Database & InfrastructureHIGHdb-
6Views & FrontendMEDIUMview-
7Code StyleMEDIUMstyle-
8TestingMEDIUMtest-

Quick Reference

1. Architecture Fundamentals (CRITICAL)

2. Controllers & REST (CRITICAL)

3. Domain Modeling (HIGH)

4. State Management (HIGH)

5. Database & Infrastructure (HIGH)

6. Views & Frontend (MEDIUM)

7. Code Style (MEDIUM)

8. Testing (MEDIUM)

How to Use

Read individual reference files for detailed explanations and code examples:

Reference Files

FileDescription
references/_sections.mdCategory definitions and ordering
assets/templates/_template.mdTemplate for new rules
metadata.jsonVersion and reference information

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/pproenca/dot-skills/37signals-rails">View 37signals-rails on skillZs</a>