rails-37signals-refactor

Refactor Rails code incrementally toward 37signals-style conventions.

1|Updated Feb 3, 2026

Search Tags:#testing #architecture #refactor #conventions #rails #incremental

Ready to run

npx skills add https://github.com/joshyorko/agent-skills --skill rails-37signals-refactor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rails-37signals-refactor
Source: https://github.com/joshyorko/agent-skills/tree/main/plugins/rails-37signals-workflows/skills/rails-37signals-refactor
Command: npx skills add https://github.com/joshyorko/agent-skills --skill rails-37signals-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Incrementally refactors Rails code toward 37signals-style conventions, enabling safer migrations from legacy patterns.

Core Features & Use Cases

Safe, incremental changes: move one responsibility at a time to model methods or concerns, backfill, and keep callers working.
Guided migration: follow conventions and refactoring guide to apply one-step changes without rewriting the whole app.
Retain test parity while evolving architecture, with feature flags or staged migrations.

Quick Start

Begin by auditing callers and tests, read the conventions and refactoring guide, then apply one small step and verify with targeted tests.

Frequently Asked Questions about rails-37signals-refactor

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

FAQPage Schema

How do I incrementally refactor Rails code to move service-object logic into models?▼

You incrementally refactor Rails code by moving one responsibility at a time into model methods or concerns, backfilling legacy paths so callers keep working without a risky full rewrite.

What is the best way to replace boolean state fields with state records in Rails?▼

Replace boolean state in Rails through staged migration: introduce state records alongside boolean fields, backfill data, and retain test parity while evolving your architecture safely.

How do I slim down Rails controllers without breaking existing functionality?▼

Slim Rails controllers by applying non-destructive, one-step changes that move logic into models, verifying each step with targeted tests while keeping legacy paths backfilled until migration completes.

Can I tighten multi-tenant scoping in Rails without a full application rewrite?▼

Yes, you tighten multi-tenant scoping without a full rewrite by following incremental refactor steps that enforce non-destructive changes, staged migrations, and preserved tests throughout the process.

How do I start an incremental Rails refactor without failing existing tests?▼

Start by auditing callers and tests, reading the conventions and refactoring guide, then applying one small step and verifying with targeted tests to retain test parity while evolving architecture.

When should I avoid incremental refactoring for Rails conventions?▼

Avoid incremental refactoring when a Rails app requires a complete architectural overhaul rather than staged migrations, since this approach relies on non-destructive steps, backfilling, and preserved tests rather than risky rewrites.