Guides TDD boundary selection for Rails changes across spec types.
npx skills add https://github.com/igmarin/rails-agent-skills --skill rails-tdd-slices
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
Deciding where to start TDD for a Rails change.
Describe a Rails change, identify the highest-value boundary for the initial spec, and write one failing example to gate the task.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
igmarinIdentify and map domain boundaries in Rails apps to prevent cross-context leakage.
FaisalAlqarniImplement test-driven development workflows for Ruby on Rails with RSpec, FactoryBot, and Capybara.
ICI-CancioneroGuide RSpec testing for Rails models, requests, and system specs.
igmarinConvert Rails bug reports into failing specs and fix plans.
