Tdd
Thin core + domain sets for a fast, stack-aware project start. Cross-agent (Claude Code, Cursor, Codex, Gemini) via the SKILL.md standard. MIT.
npx -y skills add Neznakometz/StackForge --skill tddAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
The mandatory order for writing code with tests. Apply whenever writing business logic.
SKILL.md
0.9 KB, as published. Nobody here has run it
TDD: red → green → refactor
- Write a test that expresses the task's requirement. Run it — it MUST fail (didn't fail → the test checks nothing, rewrite it).
- Minimal code until green. Don't implement "for the future" (YAGNI).
- Refactor while the tests are green. Commit.
Rules:
- External providers (API, payments, ASR/LLM) — only mocks in tests; real keys in tests = a mistake.
- Test behavior, not implementation: reliance on private fields/the call order of mocks is brittleness.
- Edge cases from the acceptance criteria: empty input, zero values, network drop, exhausted limit, timeout.
- No
sleepin tests — fake timers / explicit awaits. - e2e — only for the phase's critical flows (listed in the acceptance criteria), everything else — with unit tests: e2e is expensive and slow.
Gives 3 of the 12 instructions most tdd skills give
Counted across 439 of the 443 authors here whose files we hold, read 2026-08-06
- write minimal code to pass the testhere, and in 302 of 439, across 218 files
- write a failing test firsthere, and in 176 of 439, across 112 files
- refactor code only after tests passin 171 of 439, across 101 files
- watch the test fail before writing codein 142 of 439, across 93 files
- test one behavior per testin 106 of 439, across 44 files
- refactor code while keeping tests greenhere, and in 99 of 439, across 86 files
- delete code written before testsin 98 of 439, across 54 files
- run tests after each refactor stepin 85 of 439, across 54 files
- Use real code instead of mocks unless unavoidablein 64 of 439, across 21 files
- confirm the test fails for the right reasonin 64 of 439, across 60 files
- reproduce bugs with a test before fixingin 53 of 439, across 36 files
- write tests before implementationin 48 of 439, across 39 files
Said here and by no other author read
- rewrite a test that does not fail
- cover edge cases from acceptance criteria
- use fake timers or explicit awaits
- run e2e only for critical flows
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.