tdd
Skill5 starsChanged 5 months agoMITView on GitHub
Test-driven development workflows and red-green-refactor loops
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
When developing new features following strict TDD constraints.
- Distinctive: line 12
When refactoring legacy code safely by writing tests first.
- Distinctive: line 15
Red: Write a failing test for the next piece of functionality.
- Distinctive: line 16
Green: Write the absolute minimum amount of code necessary to make the test pass.
- Distinctive: line 18
Wait on edge cases: Don't write generalized code until the tests explicitly demand it through diverse test cases.
“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 (TDD) Skill
This skill guides the implementation of features using the TDD lifecycle.
When to use this skill
- When developing new features following strict TDD constraints.
- When refactoring legacy code safely by writing tests first.
Guidelines
- Red: Write a failing test for the next piece of functionality. Ensure it fails for the correct reason.
- Green: Write the absolute minimum amount of code necessary to make the test pass.
- Refactor: Improve the code quality, remove duplication, and optimize while ensuring tests remain green.
- Wait on edge cases: Don't write generalized code until the tests explicitly demand it through diverse test cases.
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- mattpocock/skills★ 309ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 40ksame name
- Yeachan-Heo/oh-my-claudecode★ 40ksame name
- QuivrHQ/quivr★ 40ksame name
- ccusage/ccusage★ 19ksame name
- ryoppippi/ccusage★ 19ksame name
- MODSetter/SurfSense★ 17ksame name
- GreyDGL/PentestGPT★ 16ksame name
- open-metadata/OpenMetadata★ 16ksame name
- prowler-cloud/prowler★ 15ksame name
183 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.
Used alongsideProjects with it also use poteto-mode, setup-pstack 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.
jtarorehSkillpoteto-mode
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
Also in 5 projects that use this
bnemaSkillsetup-pstack
Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.
Also in 22 projects that use this
jaydubya818Skillprinciple-laziness-protocol
Apply when a refactor is adding wrappers or abstractions instead of simplifying.
Also in 38 projects that use this
- jaydubya818Skill
principle-make-operations-idempotent
Apply when an operation must tolerate retries after partial completion.
Also in 38 projects that use this
- +8 more from jaydubya818
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codex/AGENTS.mdAGENTS.md
- claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- fastapiSkill
- rustSkill
- backend-codeSkill
- frontend-codeSkill
- javascript-codeSkill
- java-codeSkill
- python-codeSkill
- codeSkill
- crash-analysisSkill
- memory-debugSkill
- network-debugSkill
- performance-debugSkill
- debugSkill
- argo-cdSkill
- dockerSkill
- github-actionsSkill
- gitlab-ciSkill
- jenkinsSkill
- kubernetesSkill
- devopsSkill
- terraformSkill
- nextjsSkill
- react-nativeSkill
- api-design-planSkill
- architecture-planSkill
- database-planSkill
- security-planSkill
- planSkill
- e2e-testSkill
- integration-testSkill
- testSkill
- unit-testSkill
- smart-contractsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.