Test-driven development (Superpowers)
SkillEnforces red-green-refactor: write a failing test first, then the minimal code to pass it.
Sets a strict rule that no production code is written until a failing test exists for it. Claude writes the test, watches it fail for the right reason, writes the smallest change that passes, then refactors. It lists the common excuses for skipping tests and how to reject them, and includes notes on writing good tests. Applies to any language or test framework.
Try asking:
- "Fix the date parsing bug, test first"
- "Add a discount-code feature using TDD"
- "Implement the rate limiter with red-green-refactor"
Source: obra/superpowers · MIT · by Jesse Vincent (obra)

Log in to join the discussion.