Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/tdd-workflow
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
Passed 23 of 24 test cases with the skill, and 18 of 24 without it.
and 4 more in the full report
5 fixed18 passed either way1 still failing0 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.
In a test-driven workflow for a file parsing utility, where do edge cases (such as zero-byte files) rank in priority relative to happy path and error cases?
| Checked | Without skill | With skill |
|---|---|---|
| Edge cases are designated as Priority 3, ranked after happy path and error cases. | Missed | Passed |
The instructions your model reads when the skill loads.
Write tests first, code second.
🔴 RED → Write failing test
↓
🟢 GREEN → Write minimal code to pass
↓
🔵 REFACTOR → Improve code quality
↓
Repeat...
| Focus | Example |
|---|---|
| Behavior | "should add two numbers" |
| Edge cases | "should handle empty input" |
| Error states | "should throw for invalid data" |
test cases passed, vs 18 / 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.