SKILL.md
Three.js QA Release
Prove the game works the way a player will meet it, then prepare a shippable build with its known risks.
Resolve <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.
References
| File | Read it when |
|---|---|
references/release-checks.md |
mobile verification, production release, performance evidence, or release-failure traps |
references/visual-test-harness.md |
screenshot baselines, visual regression, UI or generated-asset regression protection |
references/playtest-bot.md |
release-ready gameplay claims, difficulty and fairness checks, or a loop never driven by scripted input |
QA pass
For 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.
Three.js QA Release
Prove the game works the way a player will meet it, then prepare a shippable build with its known risks.
Resolve <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.
References
| File | Read it when |
|---|---|
references/release-checks.md |
mobile verification, production release, performance evidence, or release-failure traps |
references/visual-test-harness.md |
screenshot baselines, visual regression, UI or generated-asset regression protection |
references/playtest-bot.md |
release-ready gameplay claims, difficulty and fairness checks, or a loop never driven by scripted input |
QA pass
For 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.