Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jamditis/test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
Passed 22 of 22 test cases with the skill, and 18 of 22 without it.
and 2 more in the full report
4 fixed18 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
To test my `retryOperation` function, I created a mock using `jest.fn().mockRejectedValueOnce(...)` and asserted on `expect(mock).toHaveBeenCalledTimes(3)`. Is this test design acceptable?
| Checked | Without skill | With skill |
|---|---|---|
| Advises testing real operation execution behavior rather than relying on mocks. | 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
test cases passed, vs 18 / 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.