Tdd

The mandatory order for writing code with tests. Apply whenever writing business logic.From its SKILL.md

Install

npx -y skills add Neznakometz/StackForge --skill tdd

Assembled 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.

0.9 KB, 195 tokens by cl100k_base, as published. Nobody here has run it

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 sleep in 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.