test-it
Installation
SKILL.md
Test It
Make the intended behavior provable with automated and/or explicit manual evidence. Discover the repo's real test stack; do not invent a new framework unless asked.
Name the quality regime first (see handbook concepts/11-quality-regimes.md):
| Regime | Prove with… |
|---|---|
| A — Deterministic compute (API/algo/analytics) | Invariants, golden/property tests, data contracts / expectation suites |
| B — Interactive product (web/fullstack) | Behavior tests + critical E2E; a11y; performance budgets / Web Vitals where relevant |
| C — Generative / high-input | Datasets + layered graders (code → LLM-judge → human); not exact free-text equality. Prefer Langfuse (or repo OTel eval stack) for experiment scores |
Hybrids: gate each surface by its own regime.
Operating contract
Shared by every DecisionNerd/dev-skills skill. Canonical copy: handbook/concepts/14-operating-contract.md.