rails-tdd-slices

Guides TDD boundary selection for Rails changes across spec types.

22|6|Updated Mar 11, 2026

Search Tags:#testing #tdd #spec #rails #rspec #boundary #slice

Ready to run

npx skills add https://github.com/igmarin/rails-agent-skills --skill rails-tdd-slices

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rails-tdd-slices
Source: https://github.com/igmarin/rails-agent-skills/tree/main/rails-tdd-slices
Command: npx skills add https://github.com/igmarin/rails-agent-skills --skill rails-tdd-slices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deciding where to start TDD for a Rails change.

Core Features & Use Cases

Boundary-driven TDD planning across request, model, service, job, system, and engine specs.
HARD-GATE guided first failing spec approach to validate the boundary before implementation.
Chain to related skills like rspec-best-practices and rails-engine-testing to complete the workflow.

Quick Start

Describe a Rails change, identify the highest-value boundary for the initial spec, and write one failing example to gate the task.

Frequently Asked Questions about rails-tdd-slices

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

FAQPage Schema

How do I decide where to start TDD for a Rails change?▼

To start TDD for a Rails change, identify the highest-value testing boundary across request, model, service, job, system, and engine specs. You then write one failing spec to gate the task and validate the boundary before implementation.

What is a HARD-GATE process in Rails TDD?▼

A HARD-GATE process in Rails TDD enforces writing a recommended first failing spec to validate a selected boundary. This approach ensures the testing boundary is confirmed before any implementation logic is written.

How do I choose the right RSpec boundary for a new Rails feature?▼

Choosing the right RSpec boundary involves evaluating request, model, service, job, system, and engine specs to find the highest-value starting point. The boundary-aware spec selection guides you to the optimal first test.

When should I use system specs versus request specs in Rails TDD?▼

System specs versus request specs selection depends on your boundary-driven TDD planning. You choose the boundary that provides the highest value for your specific Rails change before writing the initial gating spec.

Can I chain Rails TDD workflows to other testing skills?▼

You can chain Rails TDD workflows to related skills like rspec-best-practices and rails-engine-testing. Chaining to these skills completes the testing workflow after you establish your initial boundary and first spec.

What is the best way to write the first failing spec for a Rails service object?▼

The best way to write the first failing spec for a Rails service object is using boundary-aware spec selection. You enforce a HARD-GATE by writing one failing example at the service boundary to validate the task before implementation.