test-driven-development
Use when implementing any feature, fixing any bug, or changing behavior in TypeScript or Python — and whenever the user mentions TDD, test-first, test-driven, red-green-refactor, "write tests", "add tests", unit/integration tests, pytest, vitest, jest, mocking/test doubles, coverage gates, or retrofitting tests onto a legacy codebase. Teaches the full TDD discipline (the Iron Law, red-green-refactor, the Three Laws, FIRST, AAA/GWT, triangulation), with extensive runnable TypeScript (Vitest) and Python (pytest) examples, test-double/mocking guidance and anti-patterns, how to bootstrap TDD into a new OR existing repo, advanced patterns (outside-in, double-loop, property-based, controlling time/IO), and WHY test-first produces better software specifically when an AI agent writes the code. This is the comprehensive companion to the terse `superpowers:test-driven-development` enforcer — use both: that one to stay disciplined in the loop, this one for depth, examples, and setup.
Score58
How is this score calculated?
- Weighted across six dimensions, scored 0-100.
- Provenance (25): listed in an official or curated registry.
- Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
- Maintenance (20): recency of the last push; archived entries score zero here.
- Adoption (20): repository stars on a log curve.
- Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
- Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
- Security signals subtract up to 20. Scores are recomputed on every daily ingest.
codex skill install joeblackwaslike/agent-skillsDetails