Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aiskillstore/tdd
Test-Driven Development workflow - write tests first, then implementation
Passed 11 of 24 test cases with the skill, and 8 of 24 without it.
and 4 more in the full report
5 fixed6 passed either way11 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
My date formatting function passes tests for valid Date instances. Now I need to handle null inputs. Should I update the code first or write a test first?
| Checked | Without skill | With skill |
|---|---|---|
| Requires writing a failing test for null input before modifying implementation. | Passed | Passed |
| Formats the test description using should [expected behavior] when [condition]. | Missed | Passed |
The instructions your model reads when the skill loads.
Follow the Red-Green-Refactor cycle strictly. Never write production code without a failing test first.
┌─────────────────────────────────────────┐
│ │
│ ┌───────┐ │
│ │ RED │ Write a failing test │
│ └───┬───┘ │
│ │ │
│ ▼ │
│ ┌───────┐ │
│ │ GREEN │ Write minimal code to pass│
│ └───┬───┘ │
│ │ │
│ ▼ │
│ ┌──────────┐ │
│ │ REFACTOR │ Improve without │
│ └────┬─────┘ breaking tests │
│ │ │
│ └──────────────────────────────┘
No production code without a failing test
Write the minimum test to fail
Write the minimum code to pass
test cases passed, vs 8 / 24 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.