superpowers-tdd

Files (1)

• SKILL.md

SKILL.md (first lines)

# Superpowers: Test-Driven Development (TDD) Skill

Use this skill whenever implementing new functionality, refactoring code, or fixing bugs.

## Core Axiom
**No production code shall be written unless a failing test requires it.**

## RED-GREEN-REFACTOR Protocol

### Phase 1: RED (Write Failing Test)
1. Write a minimal unit, integration, or E2E test describing the expected behavior.
2. Run the test suite and confirm:
   - The test **fails**.
   - The failure reason matches the expected missing feature (not a syntax error or typo).

### Phase 2: GREEN (Make Test Pass)
1. Write the **minimal** production code required to make the failing test pass.
2. Do not add speculative code, extra fields, or future features.
3. Run the test suite and confirm the test **passes**.

### Phase 3: REFACTOR (Clean Code)
1. Refactor the code for clarity, performance, and adherence to design patterns.
2. Ensure all tests remain **100% GREEN**.

## Testing Anti-Patterns to Avoid
- **Testing Implementation Details**: Test contracts and outputs, not internal private variables.
- **Flaky Tests**: Avoid hardcoded delays (`sleep(1000)`). Use dynamic assertion waiting.
- **Deleting Tests to Pass**: Never delete or comment out failing assertions to claim completion.

From karim-embarek/superpowers-antigravity, MIT.

More from karim-embarek/superpowers-antigravity