Install any skill in seconds. Free to start, no credit card required.
Get Started Free →freedomintelligence/test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
Passed 20 of 22 test cases with the skill, and 10 of 22 without it.
and 15 more in the full report
10 fixed10 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have a failing test checking if `formatCurrency(100)` returns `'$100.00'`. Provide the TypeScript implementation for `formatCurrency` to make this test pass.
| Checked | Without skill | With skill |
|---|---|---|
| The implementation contains only minimal logic necessary to pass the test. | Missed | Passed |
| The code omits optional parameters such as custom locales or formatting options. | Missed | Passed |
The instructions your model reads when the skill loads.
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
Violating the letter of the rules is violating the spirit of the rules.
Always:
Exceptions (ask your human partner):
Thinking "skip TDD just this once"? Stop. That's rationalization.
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
Write code before the test? Delete it. Start over.
No exceptions:
Implement fresh from tests. Period.
test cases passed, vs 10 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.