Test Driven Development
Use this skill when the behavior can be expressed clearly in tests before the implementation is obvious.
Preferred Flow
- Write or identify the failing test first.
- Make the minimal change that turns it green.
- Refactor only after behavior is protected.
- Keep the test focused on one behavior.
Guardrails
- Do not add broad, fragile snapshot coverage when a precise assertion is possible.
- If the repo has a stronger existing testing pattern, follow it.