Three.js QA Release
Prove the app or game works as its user encounters it and that the production
build is shippable.
Read ../../references/verification-policy.md first. Do not start browser,
Playwright, canvas, screenshot, diagnostics, release-preview, or mobile work
without approval for that scope.
Read By Need
- Core QA, responsive behavior, performance, evidence, and release:
references/qa-release-checklists.md.
- Screenshot baselines or visual regression:
references/visual-test-harness.md.
- Game-only scripted play, difficulty, fairness, or softlocks:
references/game-playtest-bot.md.
Default Minimum
Without additional approval, run only the policy's automatic minimum: the
smallest build/typecheck gate, focused existing non-browser tests, and local
asset/import-path checks. Fix owned failures, then state that extended browser
QA was not run and offer a concrete desktop QA pass.
Approved Desktop QA Workflow
- Confirm the approved scope, then start the intended dev or production
preview.
- Capture console, page, and relevant network errors.
- Verify nonblank canvas pixels and the approved active desktop view.
- Exercise the primary user journey and changed risky paths.
- Test loading, empty, unsupported, and error states when applicable.
- Check desktop UI fit, input cancellation, and resize.
- If audio changed, verify gesture unlock, decode/load, triggers, loops,
cleanup, mute, and volume.
- Add deterministic screenshot baselines only when separately approved;
otherwise record that they were not run.
- Run canvas diagnostics, profiling, production-preview checks, or game bot
playtests only when the user approved those checks.
- Record commands, artifacts, issues, and remaining risks.
After desktop QA, offer mobile as a separate second step. Do not infer mobile
approval from desktop approval.
Canvas Inspector
After canvas-inspector approval, run from the target project so its
@playwright/test and pngjs dependencies are used:
node <this-skill-dir>/scripts/inspect-threejs-canvas.mjs --url http://127.0.0.1:5188
Add --mobile, --state <name>, and --seed <n> as needed. The JSON
contains canvas metrics and renderer-budget comparisons. Blank/error conditions
exit nonzero.
The game scaffold creator copies this canonical inspector into generated games,
so they remain self-contained without duplicated source.
Approved Release Workflow
- Inspect scripts, Vite
base, public assets, and deployment assumptions.
- Gate debug UI, verbose logging, and test helpers.
- Run production build and preview.
- Recheck desktop/mobile interaction and asset paths in built output.
- Review bundle size, large assets, and third-party asset notices.
- Report deployment commands and residual risks.
Final Response
Lead with pass/fail. Include commands, URL, primary journey or game loop,
controls, screenshots/artifacts, issues, canvas/performance evidence, visual
harness and game-bot decisions when relevant, deployment notes, and risks.
Always disclose extended browser QA that was not run and whether mobile still
requires approval.
1---2name: threejs-qa-release3description: "Verify and release Three.js apps and games through primary-journey QA, desktop/mobile visual checks, canvas metrics, visual regression, optional game bot playtests, production previews, and release-risk reporting."4metadata:5 source: https://skillmd.com/skills/mintdotgg/threejs-qa-release6---78# Three.js QA Release910Prove the app or game works as its user encounters it and that the production11build is shippable.1213Read `../../references/verification-policy.md` first. Do not start browser,14Playwright, canvas, screenshot, diagnostics, release-preview, or mobile work15without approval for that scope.1617## Read By Need1819- Core QA, responsive behavior, performance, evidence, and release:20 `references/qa-release-checklists.md`.21- Screenshot baselines or visual regression:22 `references/visual-test-harness.md`.23- Game-only scripted play, difficulty, fairness, or softlocks:24 `references/game-playtest-bot.md`.2526## Default Minimum2728Without additional approval, run only the policy's automatic minimum: the29smallest build/typecheck gate, focused existing non-browser tests, and local30asset/import-path checks. Fix owned failures, then state that extended browser31QA was not run and offer a concrete desktop QA pass.3233## Approved Desktop QA Workflow34351. Confirm the approved scope, then start the intended dev or production36 preview.372. Capture console, page, and relevant network errors.383. Verify nonblank canvas pixels and the approved active desktop view.394. Exercise the primary user journey and changed risky paths.405. Test loading, empty, unsupported, and error states when applicable.416. Check desktop UI fit, input cancellation, and resize.427. If audio changed, verify gesture unlock, decode/load, triggers, loops,43 cleanup, mute, and volume.448. Add deterministic screenshot baselines only when separately approved;45 otherwise record that they were not run.469. Run canvas diagnostics, profiling, production-preview checks, or game bot47 playtests only when the user approved those checks.4810. Record commands, artifacts, issues, and remaining risks.4950After desktop QA, offer mobile as a separate second step. Do not infer mobile51approval from desktop approval.5253## Canvas Inspector5455After canvas-inspector approval, run from the target project so its56`@playwright/test` and `pngjs` dependencies are used:5758```bash59node <this-skill-dir>/scripts/inspect-threejs-canvas.mjs --url http://127.0.0.1:518860```6162Add `--mobile`, `--state <name>`, and `--seed <n>` as needed. The JSON63contains canvas metrics and renderer-budget comparisons. Blank/error conditions64exit nonzero.6566The game scaffold creator copies this canonical inspector into generated games,67so they remain self-contained without duplicated source.6869## Approved Release Workflow70711. Inspect scripts, Vite `base`, public assets, and deployment assumptions.722. Gate debug UI, verbose logging, and test helpers.733. Run production build and preview.744. Recheck desktop/mobile interaction and asset paths in built output.755. Review bundle size, large assets, and third-party asset notices.766. Report deployment commands and residual risks.7778## Final Response7980Lead with pass/fail. Include commands, URL, primary journey or game loop,81controls, screenshots/artifacts, issues, canvas/performance evidence, visual82harness and game-bot decisions when relevant, deployment notes, and risks.83Always disclose extended browser QA that was not run and whether mobile still84requires approval.