Menu
Test the boundary between two systems by the contract, not the implementation. Use for APIs, integrations, and shared interfaces.
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
Calibrate a reviewer persona with few-shot rubric examples so skepticism stays consistent and doesn't drift lenient over long runs.
Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order. The ledger fresh-context sessions read to know what's done, what's next, and what they're forbidden to touch.
Systematically remove one harness component at a time and measure impact, killing scaffolding that no longer earns its complexity.
Author idempotent init.sh under 120s plus sibling test.sh, stop.sh, reset.sh, serve.sh with fixed names the harness relies on.
Expand a 1-4 sentence product brief into a full spec with a design language, acceptance surface, and an ordered feature list.
Run the fixed 6-step session-opening sequence — pwd, read progress, git log, count remaining features, init.sh, smoke-test last feature — before touching any new work. The orientation ritual that lets fresh-context sessions reconstruct project state in under a minute.
| name | contract-test |
| description | Test the boundary between two systems by the contract, not the implementation. Use for APIs, integrations, and shared interfaces. |
| when_to_use | an API endpoint, a service integration, a webhook, a shared schema |
Test what the two sides AGREED on, so either can change internals without breaking the other.
