test-driven-development
This Claude Code skill enforces strict test-driven development discipline by requiring the RED-GREEN-REFACTOR cycle in all BUILD workflows. It mandates that failing tests be written first with exit code 1, followed by minimal implementation with exit code 0, then refactoring while maintaining passing tests. The skill prohibits watch mode and deferred testing, uses run mode exclusively with timeout guards, and requires exit code evidence at each phase to prevent incomplete cycles and hanging processes.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/test-driven-development && cp -r /tmp/test-driven-development/library/methodologies/cc10x/skills/test-driven-development ~/.claude/skills/test-driven-developmentSKILL.md
## Non-Negotiable Rules - Always use run mode (`CI=true npm test` or `--run` flag) - NEVER use watch mode (prevents hanging processes) - Use timeout guards (`timeout 60s`) as backup - Record exit codes as evidence at each phase - If tests fail 3 consecutive times in GREEN, report failure status - Never skip RED phase (failing test must exist before implementation) - Never defer tests to "later" -- TDD means tests first ## Scope Discipline - If implementation requires >3 file changes, flag for scope review - Architectural choices require user approval unless pre-approved in plan - New dependencies require user approval ## When to Use - Every feature implementation in BUILD workflow - Every bug fix in DEBUG workflow (regression test) ## Agents Used - `component-builder` (primary consumer) - `bug-investigator` (regression tests)
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.