tdd
Skill1 starsChanged 34 days agoMITView on GitHub
Red-green-refactor execution loop for behavior-changing code — use when executing a step Task that declares Seams under test, or when building a feature or fixing a bug test-first. Laravel projects using Sail.
194 other projects use a version of this, 62 of them edited.
Adopted by
Most recently taken up by
- lhotwll217/owner-operatoredited, first seen Nov 16, 2026
- philoserf/claude-code-configedited, first seen Nov 15, 2026
- e2b-dev/E2Bedited, first seen Nov 15, 2026
- backnotprop/pstacktheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewedited, 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 silent 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 · 62
- mattpocock/skills★ 325k20% same
- QuivrHQ/quivr★ 40k11% same
- The-Vibe-Company/quivr★ 40k11% same
- MODSetter/SurfSense★ 17k20% same
- e2b-dev/E2B★ 15k16% same
- formbricks/formbricks★ 13k20% same
- ArcReel/ArcReel★ 6.6k20% same
- withcoral/coral★ 4.9k20% same
- bestofjs/bestofjs★ 3.1k20% same
- crbnos/carbon★ 2.8k20% same
52 more not listed
Wrote their own version · 132
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- trpc/trpc★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- ryoppippi/ccusage★ 19ksame name
- ccusage/ccusage★ 19ksame name
- GreyDGL/PentestGPT★ 16ksame name
- open-metadata/OpenMetadata★ 16ksame name
- prowler-cloud/prowler★ 15ksame name
- FastLED/FastLED★ 7.5ksame name
- sanity-io/sanity★ 6.4ksame name
122 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 repository7 other files it gives its agents.
- guidelines/agents.mdAGENTS.md
- code-reviewSkill
- eurekaSkill
- plansSkill
- resource-first-controllersSkill
- security-reviewSkill
- sequential-implementation-orchestrationSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
3
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 15
If a seam turns out to be wrong or missing mid-step, stop and confirm with the owner — it is a plan deviation, not an executor decision.
- Distinctive: line 19
Red before green: Write the failing test first, then only enough implementation to pass it.
- Distinctive: line 27
Horizontal slicing: all tests first, then all implementation.
“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 is the red → green loop: one failing test, then only the code that makes it pass, repeated in vertical slices. This skill disciplines the loop so it produces tests worth keeping; what a good test is (assertion quality, AAA, naming, isolation) lives in the repo's guideline docs (guidelines/coding-style.md, guidelines/testing.md) and the pest-testing skill where the repository ships it — consult them, don't restate them here.
Seams
A seam is a public boundary where behavior is observable: the interface you test through without reaching inside. Tests live at seams, never against internals.
- Seams are declared in the step Task body (
Seams under test) and confirmed at owner review. No test is written at an undeclared seam — that is how testing effort lands on the critical paths and the complex logic, not on every edge case. - If a seam turns out to be wrong or missing mid-step, stop and confirm with the owner — it is a plan deviation, not an executor decision.
Rules of the loop
- Red before green. Write the failing test first, then only enough implementation to pass it. Don't anticipate future tests or add speculative features.
- One slice at a time. One seam, one test, one minimal implementation per cycle, each a tracer bullet that responds to what the last cycle taught you.
- Refactoring is not part of the loop. It belongs to review, after the step's behavior is green.
Anti-patterns
- Implementation-coupled: mocks internal collaborators, tests private methods, or verifies through a side channel. The tell: the test breaks on a refactor that changes no behavior.
- Tautological: the assertion recomputes the expected value the way the code does, so it passes by construction. Expected values come from an independent source of truth: a known-good literal, a worked example, the spec.
- Horizontal slicing: all tests first, then all implementation. Bulk tests verify imagined behavior. Work vertical instead: one test → one implementation → repeat.
Rhythm
- During the loop: run the single test file after every cycle (
vendor/bin/sail artisan test --compact --parallel tests/Feature/XTest.php). - At step close: the step Task's full verification, then Duster — per the
plansskill. - Close runs on the owner's stage signal: commit the step's code
(#NN)when it has one (verification-only →Commit: none — verification-only) → as-built resolution comment on the Task → Task Done. No mid-step commits; the loop's work stays unstaged until review.
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.

