
from stevesolun494
Guided workflow and principles for test-driven development using the red-green-refactor loop.
Core principle: write tests that verify behavior through public interfaces, not implementation details. This skill documents a practical TDD workflow: planning, tracer-bullet vertical slices (one test → one implementation), an incremental red→green loop, and refactor guidance.
It includes anti-patterns to avoid (e.g., horizontal slicing), a per-cycle checklist, and links to companion notes (tests.md, mocking.md, refactoring.md, interface-design.md) for examples and deeper guidance.
Use when: the user asks to develop features or fix bugs using TDD, requests integration-style tests, or explicitly mentions "red-green-refactor" or test-first development.
Pure instructional skill guiding agents through the TDD red-green-refactor cycle. No scripts or executable code — entirely SKILL.md content with referenced supplementary docs (seams.md, mocking.md, bugfixes.md, etc.). Well-structured with clear anti-patterns, entry paths for features/bugs/legacy, and feedback speed guidance. No security concerns whatsoever.
Clean, well-authored instructional skill. The subagent section could use a note about not granting subagents access to sensitive resources. Referenced supplementary files are a nice touch for progressive disclosure but cannot be verified as present.