rails-tdd-slices

Use when choosing the best first failing RSpec spec or vertical slice for a Ruby on Rails change. Covers request vs model vs service vs job vs engine spec selection, system spec escalation, smallest safe slice planning, and Rails-first TDD sequencing. Trigger words: where to start testing, what test to write first, RSpec, test-driven development, TDD, first failing test.

Ir a la instalación

Repositorio: midudev/autoskills
Última actividad en el origen: 24 de abril de 2026 a las 21:22
Idioma detectado de SKILL.md: inglés
Estrellas: 6776
Forks: 616

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/midudev/autoskills --skill rails-tdd-slices

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

name	rails-tdd-slices
license	MIT
description	Use when choosing the best first failing RSpec spec or vertical slice for a Ruby on Rails change. Covers request vs model vs service vs job vs engine spec selection, system spec escalation, smallest safe slice planning, and Rails-first TDD sequencing. Trigger words: where to start testing, what test to write first, RSpec, test-driven development, TDD, first failing test.

Rails TDD Slices

Use this skill when the hardest part of the task is deciding where TDD should start.

Core principle: Start at the highest-value boundary that proves the behavior with the least unnecessary setup.

Quick Reference

Change type	First spec	Path	Why
API contract, params, status code, JSON shape	Request spec	`spec/requests/`	Proves the real HTTP contract
Domain rule on a cohesive record or value object	Model spec	`spec/models/`	Fast feedback on domain behavior
Multi-step orchestration across collaborators	Service spec	`spec/services/`	Focuses on the workflow boundary
Enqueue/run/retry/discard behavior	Job spec	`spec/jobs/`	Captures async semantics directly
Critical Turbo/Stimulus or browser-visible flow	System spec

Pitfall	What to do
Starting with a PORO spec because it is easy	Easy ≠ high-signal — choose the boundary that proves the real behavior
Writing three spec types before running any	Pick one slice, run it, prove the failure, then proceed
Defaulting to request specs for everything	Some domain rules are better proven at the model or service layer
Defaulting to model specs for controller behavior	Controllers and APIs need request-level proof
Using controller specs as the default HTTP entry point	Prefer request specs unless the repo has an existing reason
Jumping to system specs too early	Reserve for critical browser flows that lower layers cannot prove
"We'll add the request spec later"	The spec is the gate — implement only after the first slice is failing for the right reason
First spec requires excessive factory setup	Excessive setup = wrong boundary. Simplify or move the slice.

Skill	When to chain
rspec-best-practices	After choosing the first slice, to enforce the TDD loop correctly
rspec-service-testing	When the first slice is a service object spec
rails-engine-testing	When the first slice belongs to an engine
rails-bug-triage	When the starting point is an existing bug report
refactor-safely	When the task is mostly structural and needs characterization tests first

rails-tdd-slices

Opciones de instalación

Revisa los archivos de origen

Rails TDD Slices

Quick Reference

Rails TDD Slices

Quick Reference

HARD-GATE

Process

Examples

Good: New JSON Endpoint

Good: New Orchestration Service

Test Feedback Checkpoint

Pitfalls

Integration

rails-tdd-slices

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

Rails TDD Slices

Quick Reference

Rails TDD Slices

Quick Reference

HARD-GATE

Process

Examples

Good: New JSON Endpoint

Good: New Orchestration Service

Test Feedback Checkpoint

Pitfalls

Integration