threejs-qa-release

1# Three.js QA Release
2 
3Prove the game works the way a player will meet it, then prepare a shippable build with its known risks.
4 
5Resolve `<this-skill-dir>` and local references from the actual loaded skill file; resolve sibling skills beside it before using runner-discovered alternatives. Run the inspector from the game project with its npm dependencies installed.
6 
7## References
8 
9| File | Read it when |
10| --- | --- |
11| `references/release-checks.md` | mobile verification, production release, performance evidence, or release-failure traps |
12| `references/visual-test-harness.md` | screenshot baselines, visual regression, UI or generated-asset regression protection |
13| `references/playtest-bot.md` | release-ready gameplay claims, difficulty and fairness checks, or a loop never driven by scripted input |
14 
15## QA pass
16 
17For a complete game use the full pass below. For narrow edits select checks covering the affected behavior, states, and target viewports. Reuse valid specialist evidence from the same code revision; the lead owns one consolidated pass. Repeat only after relevant changes, failures, or unresolved concerns. An explicit desktop-only scope does not require adding mobile gameplay.
18 
191. Install dependencies, run build and typecheck, start the dev or preview server.
202. Open the browser target and capture console, page, and network errors.
213. Confirm non-blank, visually varied canvas pixels.
22…