What problem does it solve? It answers how to set up, build, test, and verify the kami-kakushi repository from a fresh clone, and explains where each check runs (commit, push, CI, nightly) so agents stop guessing about gates, ports, and hooks. ## Core Features & Use Cases - Fresh-clone setup runbook: Node 24 via .nvmrc, pnpm 10.33.0, frozen-lockfile install, git hooks path, and the shared dev server on port 5264. - Verify anatomy: the gates.ts single source of truth, parallel runner modes, the 5s-soft/8s-hard commit budget, @slow commit-vs-push lanes, and VERIFY_FULL semantics. - CI workflow map and traps: seven GitHub workflows, nightly canary, dev-server law (never start your own :5264 server, e2e owns :5265), plus known traps like the banned pnpm version and the tsgo typechecker. - Use Case: An agent resumes work on the repo cold and asks how to run tests or why a commit was blocked; this skill provides the execution truth table and budget rules immediately. ## Quick Start Ask how to set up and verify the kami-kakushi repo from a fresh clone and which checks run at commit, push, and CI time.