Three.js QA Release
Purpose
Prove the game works as a player encounters it, then prepare a shippable browser build with known risks.
QA Workflow
Load references/qa-release-checklists.md as the first action before broad QA, mobile verification, bug reporting, production preview, static-hosting checks, or release preparation. Track it in a reference ledger with yes/no, path, and failure reason. Do not mark QA/release complete while this reference is skipped for QA or release work.
Load references/checklists/visual-verification.md for screenshot/canvas verification, references/checklists/playtest-qa.md for player-loop QA, and references/checklists/release.md for production release checks. Load references/prompt-templates.md only when the user asks for reusable QA/release prompts or a task template.
- Install dependencies if needed.
- Run build/typecheck.
- Start dev or preview server.
- Open browser target.
- Capture console/page/network errors.
- Verify nonblank canvas pixels.
- Capture desktop and mobile screenshots.
- Trigger main input, objective progression, fail/retry, and recent risky paths.
- Check HUD text fit, safe areas, touch targets, responsive layout.
- If audio changed, verify user-gesture unlock, SFX triggers, ambience loop start/stop, pause/restart cleanup, mute/volume behavior, and decode/load errors.
- Record artifacts and issues.
Packaged Canvas Inspector
Use the bundled inspector when the target project does not already include one:
node <this-skill-dir>/scripts/inspect-threejs-canvas.mjs --url http://127.0.0.1:5188
For mobile emulation, add --mobile. Generated games from the packaged scaffold also include their own scripts/inspect-threejs-canvas.mjs and npm run inspect:canvas.
Release Workflow
- Inspect package scripts, Vite config, base path, public/assets.
- Gate debug UI/logging/test helpers.
- Run production build and preview/static server.
- Verify built output desktop/mobile.
- Review bundle and large assets.
- Document deploy command, host assumptions, and residual risks.
Final Response
Lead with pass/fail. Include the reference ledger, QA matrix/checklist result, commands, URL, controls, screenshots/artifacts, issues found/fixed, deployment notes, and risks.
1---2name: threejs-qa-release3description: Verify and release Three.js browser games. Combines playtest QA, mobile/responsive checks, production builds, preview verification, static-hosting base paths, debug gating, bundle review, screenshots, packaged canvas-pixel inspection, console checks, and release risk reports.4---56# Three.js QA Release78## Purpose910Prove the game works as a player encounters it, then prepare a shippable browser build with known risks.1112## QA Workflow1314Load `references/qa-release-checklists.md` as the first action before broad QA, mobile verification, bug reporting, production preview, static-hosting checks, or release preparation. Track it in a reference ledger with yes/no, path, and failure reason. Do not mark QA/release complete while this reference is skipped for QA or release work.1516Load `references/checklists/visual-verification.md` for screenshot/canvas verification, `references/checklists/playtest-qa.md` for player-loop QA, and `references/checklists/release.md` for production release checks. Load `references/prompt-templates.md` only when the user asks for reusable QA/release prompts or a task template.17181. Install dependencies if needed.192. Run build/typecheck.203. Start dev or preview server.214. Open browser target.225. Capture console/page/network errors.236. Verify nonblank canvas pixels.247. Capture desktop and mobile screenshots.258. Trigger main input, objective progression, fail/retry, and recent risky paths.269. Check HUD text fit, safe areas, touch targets, responsive layout.2710. If audio changed, verify user-gesture unlock, SFX triggers, ambience loop start/stop, pause/restart cleanup, mute/volume behavior, and decode/load errors.2811. Record artifacts and issues.2930## Packaged Canvas Inspector3132Use the bundled inspector when the target project does not already include one:3334```bash35node <this-skill-dir>/scripts/inspect-threejs-canvas.mjs --url http://127.0.0.1:518836```3738For mobile emulation, add `--mobile`. Generated games from the packaged scaffold also include their own `scripts/inspect-threejs-canvas.mjs` and `npm run inspect:canvas`.3940## Release Workflow41421. Inspect package scripts, Vite config, base path, public/assets.432. Gate debug UI/logging/test helpers.443. Run production build and preview/static server.454. Verify built output desktop/mobile.465. Review bundle and large assets.476. Document deploy command, host assumptions, and residual risks.4849## Final Response5051Lead with pass/fail. Include the reference ledger, QA matrix/checklist result, commands, URL, controls, screenshots/artifacts, issues found/fixed, deployment notes, and risks.
Oliyflemishspeaking560