菜单
Write a failing test first, watch it fail, then write the minimal code to pass
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
