kami-build-and-env

Documents the kami-kakushi build, verify, CI, and dev-server environment runbook.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/Raynos/kami-kakushi --skill kami-build-and-env-raynos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kami-build-and-env
Source: https://github.com/Raynos/kami-kakushi/tree/main/.claude/skills/kami-build-and-env
Command: npx skills add https://github.com/Raynos/kami-kakushi --skill kami-build-and-env-raynos

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about kami-build-and-env

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up the kami-kakushi repo from a fresh clone?

Use Node 24 via .nvmrc and pnpm 10.33.0, run pnpm install --frozen-lockfile, ensure git config core.hooksPath is .githooks, then run pnpm run verify. The running game is served on the shared dev server at http://localhost:5264.

How does the pre-commit verify budget work?

The pre-commit hook times pnpm run verify; over 5 seconds warns and over 8 seconds blocks the commit. The fix is tagging slow tests with a // @slow pragma so they move to the push lane, never widening the budget; SKIP_BUDGET=1 is the escape hatch.

What is the difference between commit and push verify lanes?

At commit, vitest skips test files carrying a // @slow pragma, keeping the lane near 3 seconds. Pre-push and CI set VERIFY_FULL=1, which runs the entire suite including @slow tests, so nothing slow leaves the machine unverified.

Can I start my own vite dev server for this repo?

No. A single shared dev server runs on port 5264 and a vite-level guard plus a PreToolUse hook block starting another. The Playwright e2e lane is the only exception, managing its own server on port 5265.

Why is pnpm version banned in this repository?

pnpm version bare-commits the shared git index, sweeping up other agents' staged work in the shared tree. Releases instead go through the human-invoked /ship skill, which uses pnpm pkg set, a pathspec commit, and an isolated worktree build.

Why does verify pass locally but e2e fail in CI?

The Playwright e2e lane runs only in CI by budget decision, so commit and push hooks stay green while e2e rots. When the pre-push advisory flags e2e-related files, run pnpm run test:e2e locally before pushing.