← ClaudeAtlas

unity-play-harnesslisted

Playtest and journey tests: a GameProbe, boot into a moment, does the runner reach the gate?
tipoLi5890/unity-dev-skills · ★ 2 · AI & Automation · score 75
Install: claude install-skill tipoLi5890/unity-dev-skills
# unity-play-harness — build the game so an agent can play it and read it A game an agent cannot drive is a game that gets checked once, by hand, by whoever happens to be at the keyboard. The work here is not testing; it is **making the game observable and reachable** so that everything else — a verification, a measurement, an answer to a complaint — becomes cheap enough to do on every change. ## Load what the situation needs | The situation | Read | |---|---| | "Playtest this"; a journey test — does the runner reach the gate, every run | the four parts below, then `reference/journeys.md` | | Designing the one-line snapshot; a value you need is not in it; reading it from eval, a command, the log or a test | `reference/probe-contract.md` | | "boot straight into the boss"; "how would a test reach this screen"; a wait that times out | `reference/situations.md` | | Writing the test that drives and samples; which invariants are worth asserting over a run | `reference/journeys.md` | | A screenshot pass over every situation; situations that must not write the player's saves; the same ids in a built player | `reference/situations.md` → "A shot list over every situation" | | A match that has to play itself; an autoplayer through the real input funnel; the smoke run that rides on it | `reference/situations.md` → "the autoplayer" · `reference/journeys.md` → "The autoplayer smoke run" | | Reading, comparing or handing over a recorded run | `reference/timeline-format.md` | | A feel rep