rails-37signals-implement

Orchestrates Rails feature development with 5-way dependency-ordered workflow spanning database to tests.

1|Updated Feb 3, 2026

Search Tags:#workflow #testing #architecture #refactoring #rails #tenancy

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

End-to-end feature work in a Rails app that follows 37signals-style conventions, translating Claude-oriented workflows into a Codex-native process to ensure consistent, scalable feature delivery.

Core Features & Use Cases

End-to-end feature work orchestration in a 37signals-style Rails codebase, covering data changes, UI flow, and tests.
Dependency-ordered workflows guiding architects through database, models, controllers, views, jobs, and deploy/runtime changes.
Guidance for architecture, tenancy, Turbo/Stimulus usage, and testing with Minitest fixtures, plus opportunities for refactoring and review across multiple skills.

Quick Start

Confirm the feature shape, read references/conventions.md and references/implementation-workflow.md, and implement in dependency order from database to tests.

Frequently Asked Questions about rails-37signals-implement

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

FAQPage Schema

How do I structure end-to-end Rails feature workflows following 37signals conventions?▼

Rails feature workflows following 37signals conventions require a dependency-ordered process spanning database changes, models, controllers, views, jobs, and tests to ensure consistent feature delivery.

What is the best way to implement Turbo and Stimulus in a Rails feature workflow?▼

Implementing Turbo and Stimulus in a Rails feature workflow involves applying 37signals-style conventions to guide UI flow and interactions within the broader dependency-ordered development process.

How do I manage tenancy decisions during Rails database refactoring?▼

Tenancy decisions during Rails database refactoring are managed by enforcing specific architectural conventions and dependency-ordered changes from the database layer through to models and controllers.

Does this Rails workflow support testing with Minitest and fixtures?▼

Yes, the Rails workflow supports testing with Minitest and fixtures, enforcing 37signals-style testing conventions as the final step in the dependency-ordered feature implementation process.

Can I use this approach for Rails code reviews and refactoring?▼

Yes, you can use this approach for Rails code reviews and refactoring, as it orchestrates end-to-end feature work and identifies refactoring opportunities across database, model, and controller layers.