tdd
Skill105 starsChanged 3 days agoMITView on GitHub
Use test-driven development for behavior-changing feature or fix work, and whenever the user mentions TDD, test-first, red-green-refactor, tracer bullets, integration tests, or public-interface behavior tests. Skip for docs-only, path-only rename, formatting-only, or purely mechanical chores unless explicitly requested.
194 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- e2b-dev/E2Btheir own version, first seen Nov 15, 2026
- backnotprop/pstacktheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
Used with
Projects with it also use capture-learning-tools, design-frontend-dev and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
The-Vibe-CompanySkillcapture-learning-tools
Turn technical conversations, bugs, CI failures, review comments,
Also in 5 projects that use this
The-Vibe-CompanySkilldesign-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to
Also in 5 projects that use this
tristanphvnSkillketchup-video
Catch the user up like /keel:ketchup, with a short subtitled video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.
Also in 14 projects that use this
jaydubya818Skillfigure-it-out
Use when novel or multi-phase work needs an auditable workflow and no narrower playbook fits.
Also in 54 projects that use this
jaydubya818Skillprinciple-laziness-protocol
Apply when a refactor is adding wrappers or abstractions instead of simplifying.
Also in 45 projects that use this
- +2 more from The-Vibe-Company
- +5 more from jaydubya818
Other versions194 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- youdotcom-oss/dx-toolkit★ 2590% same
- youdotcom-oss/mcp★ 2590% same
Wrote their own version · 192
- mattpocock/skills★ 325ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- trpc/trpc★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- ryoppippi/ccusage★ 19ksame name
- ccusage/ccusage★ 19ksame name
- MODSetter/SurfSense★ 17ksame name
- GreyDGL/PentestGPT★ 16ksame name
182 more not listed
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.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- grill-meSkill
- karpathy-guidelinesSkill
- you-discoverSkill
- you-financeSkill
- you-researchSkill
- you-webSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 12 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
RED: write one test for one observable behavior.
- Distinctive: line 18
Do not write a batch of imagined tests before implementation.
- Very specific: line 23
Use bun test for targeted tests and bun --bun tsc --noEmit for the type gate.
- Very specific: line 24
Use test, not it, and organize with describe.
- Distinctive: line 25
Prefer real dependencies and real runtime boundaries over mocks.
- Distinctive: line 27
Avoid conditional assertions: assert the branch first, then assert branch-specific values.
- Distinctive: line 28
Test both branches for conditionals, fallbacks, and error paths.
- Distinctive: line 30
Follow applicable repo skills and AGENTS.md rules for the touched area.
- Distinctive: line 37
Ask one concise question only when the decision cannot be discovered and a reasonable assumption would be risky.
- Distinctive: line 40
Before writing production code, identify:
- Distinctive: line 51
Add or update exactly one focused test.
- Distinctive: line 52
Run the targeted test and confirm it fails for the intended reason.
- Distinctive: line 54
Run the same targeted test and confirm it passes.
- Distinctive: line 57
If the test passes before production code changes, it is not a valid RED signal.
“Common” is measured: kept by at least 6 in 10 of the 186 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test-Driven Development
Core Rule
Work in vertical red-green-refactor slices:
- RED: write one test for one observable behavior.
- GREEN: implement the smallest production change that makes that test pass.
- REFACTOR: clean up only while tests are green.
Do not write a batch of imagined tests before implementation. Each new test should respond to what the last cycle taught you about the actual behavior and interface.
Plaited Defaults
- Use
bun testfor targeted tests andbun --bun tsc --noEmitfor the type gate. - Use
test, notit, and organize withdescribe. - Prefer real dependencies and real runtime boundaries over mocks.
- Mock only external boundaries such as remote APIs, time, randomness, or rare filesystem cases.
- Avoid conditional assertions: assert the branch first, then assert branch-specific values.
- Test both branches for conditionals, fallbacks, and error paths.
- Exercise public interfaces and runtime contracts rather than private helpers.
- Follow applicable repo skills and
AGENTS.mdrules for the touched area.
When Starting Work
Explore the codebase first. If the public interface, expected behavior, or risk boundary is discoverable from code, tests, or docs, use that evidence instead of asking the user.
Ask one concise question only when the decision cannot be discovered and a reasonable assumption would be risky. Include your recommended answer.
Before writing production code, identify:
- the public interface or runtime boundary under test
- the first observable behavior to prove
- the targeted test command for the cycle
- the broader validation needed before handoff
Cycle Discipline
For each behavior:
- Add or update exactly one focused test.
- Run the targeted test and confirm it fails for the intended reason.
- Implement only enough code to pass.
- Run the same targeted test and confirm it passes.
- Refactor if useful, then rerun the affected tests.
If the test passes before production code changes, it is not a valid RED signal. Tighten the test, choose a different behavior, or explain why existing coverage already proves the behavior.
Reference Files
- references/tests.md: behavior-test examples and implementation-detail red flags
- references/mocking.md: boundary-only mocking guidance
- references/interface-design.md: testable public interface design
- references/deep-modules.md: small interface, deep implementation guidance
- references/refactoring.md: refactor checks to run after green
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.

