superpowers-tdd
Skill2 starsChanged 3 months agoMITView on GitHub
Enforces Test-Driven Development (RED-GREEN-REFACTOR cycle). Ensures failing tests precede code implementation and eliminates untested slop.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ErrorNotFound808/claude-skillstheir own version, first seen Oct 8, 2026
- ToussaintKnight/superpowers-workbuddytheir own version, first seen May 26, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ToussaintKnight/superpowers-workbuddy★ 2same name
- ErrorNotFound808/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill whenever implementing new functionality, refactoring code, or fixing bugs.
- Distinctive: line 16
Write a minimal unit, integration, or E2E test describing the expected behavior.
- Distinctive: line 17
Run the test suite and confirm:
- Distinctive: line 22
Write the minimal production code required to make the failing test pass.
- Distinctive: line 23
Do not add speculative code, extra fields, or future features.
- Distinctive: line 24
Run the test suite and confirm the test passes.
- Distinctive: line 28
Ensure all tests remain 100% GREEN.
- Distinctive: line 31
Testing Implementation Details: Test contracts and outputs, not internal private variables.
- Very specific: line 32
Flaky Tests: Avoid hardcoded delays (sleep(1000)).
- Distinctive: line 33
Deleting Tests to Pass: Never delete or comment out failing assertions to claim completion.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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)
- Write a minimal unit, integration, or E2E test describing the expected behavior.
- 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)
- Write the minimal production code required to make the failing test pass.
- Do not add speculative code, extra fields, or future features.
- Run the test suite and confirm the test passes.
Phase 3: REFACTOR (Clean Code)
- Refactor the code for clarity, performance, and adherence to design patterns.
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.