From rails-37signals-workflows
Use when incrementally refactoring a Rails codebase toward 37signals-style conventions, such as moving service-object logic into models, replacing boolean state with state records, slimming controllers, shifting from Sidekiq or RSpec patterns, or tightening multi-tenant scoping without a risky rewrite.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rails-37signals-workflows:rails-37signals-refactorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the goal is not a brand-new feature, but a safer path from an existing Rails shape toward 37signals-style architecture. The emphasis is incremental change, behavior preservation, and keeping tests green between steps.
Use this skill when the goal is not a brand-new feature, but a safer path from an existing Rails shape toward 37signals-style architecture. The emphasis is incremental change, behavior preservation, and keeping tests green between steps.
references/conventions.md for the destination architecture.references/refactoring-guide.md before changing multiple files or data structures.Current.account access.references/conventions.md: baseline architecture and style defaults.references/refactoring-guide.md: common migration patterns and safety rails.npx claudepluginhub joshyorko/agent-skillsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.