bootstrap-harnesslisted

# bootstrap-harness Create a production-quality harness (docs system for AI agents) in any repo. **3 progressive stages** — produce only what the project needs at its current maturity. File templates live in [templates.md](templates.md) — read it when you reach Step 3, not before. ## When to use - **Fresh repo / no CLAUDE.md** — just cloned or scaffolded, wants AI-agent workflow - **Repo with no harness** — team adopting structured AI coding - **Major rebuild** — current docs bloated / stale / drifted ## When NOT to use - **Minor tweaks / drift** → `/review-harness` (incremental, no rebuild) - **Single-file script / experiment** → overkill - **Harness exists and mostly accurate** → `/review-harness` first to confirm --- ## Core principles (2025-2026 research) 1. **Commands go first** — agents query build/test/run most often (GitHub 2,500-repo study). 2. **✅ / ⚠️ / 🚫 three-tier Boundaries** — Always / Ask first / Never (AGENTS.md spec). 3. **CORRECT / INCORRECT code pairs** — concrete examples beat prose; pull from real repo code. 4. **CLAUDE.md hard limit < 60 lines.** SOTA: instruction-following degrades past ~150-200 total instructions, and — worse — a bloated file gets judged "irrelevant" and **ignored wholesale**, taking your good rules down with it. Design CLAUDE.md as a **pointer, not a description**. Test every line: *"would removing this cause the agent to make a mistake?"* If no, cut it. Other harness files target < 200. 5. **No premature quantification** —