Menu
Write a failing test first, watch it fail, then write the minimal code to pass
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags
Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done
Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable
Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed
Author or connect a Model Context Protocol server so an agent gains new tools
Build automated pipelines that gate merges and ship reliably
| name | test-driven-development |
| description | Write a failing test first, watch it fail, then write the minimal code to pass |
| version | 1 |
| trust | built-in |
Use this whenever you add or change behaviour. The discipline is what makes the test trustworthy — a test you never saw fail proves nothing.
If a test is hard to write, the design is usually too coupled — simplify the interface before continuing.
