Three.js QA Release
FreeAutomate QA and release processes for Three.js games.
Free · Opens the source repo
What Three.js QA Release does
The Three.js QA Release skill is designed for developers working with browser-based games built using Three.js. It streamlines the quality assurance (QA) and release processes by providing a comprehensive set of checklists and automated tools. By following the structured workflow outlined in the skill, developers can ensure that their games are thoroughly tested for functionality, responsiveness, and visual integrity before they are released to players. This skill is particularly useful for teams looking to maintain high standards of quality in their game releases, reducing the risk of bugs and performance issues after deployment.
At the core of the skill is a series of checklists that guide users through various stages of QA, including mobile verification, bug reporting, and production preview. The skill emphasizes the importance of documenting the QA process in a reference ledger, allowing developers to track issues and resolutions systematically. This structured approach helps teams identify potential risks and ensures that all critical aspects of the game are evaluated before it goes live.
Additionally, the skill includes a bundled canvas inspector that can analyze the game's rendering performance and visual quality. This tool captures metrics such as color entropy and edge density, providing developers with measurable evidence of the game's graphical fidelity. By integrating automated bot playtests, the skill also allows for gameplay verification, ensuring that the game is not only visually appealing but also engaging and fair for players.
Overall, the Three.js QA Release skill is an essential tool for developers and designers who want to ensure their Three.js games are polished and ready for release. It combines manual checks with automated processes to deliver a robust QA solution that can save time and improve the quality of the final product.
When to use it
Use this skill when preparing a Three.js game for release to ensure comprehensive QA and risk assessment.
When not to use it
This skill may not be suitable for projects that do not require extensive QA processes or for games that are not built with Three.js.
What you can build with it
Preparing for Game Release
Use this skill to conduct thorough QA checks and prepare your Three.js game for a successful release.
Automated Visual Testing
Leverage the canvas inspector to automate visual quality assessments and ensure your game's graphics meet standards.
Conducting Playtests
Utilize the bot playtest feature to verify gameplay mechanics and balance before launching your game.
How to install Three.js QA Release
View source1. Install with the skills CLI
npx skills add majidmanzarpour/threejs-game-skills/threejs-qa-release --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by majidmanzarpourThree.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.
Load references/visual-test-harness.md and references/checklists/visual-test-harness.md when the game warrants screenshot baselines, visual regression testing, release-ready visual evidence, UI/generated-asset regression protection, or premium visual QA. If a harness is not warranted, report the skip reason.
Load references/playtest-bot.md and references/checklists/bot-playtest.md for release-ready gameplay claims, difficulty/fairness verification, or when the playable loop has never been driven by scripted input. Report the bot playtest decision as added/extended/skipped with reason.
- 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.
- Decide whether to add or extend a visual test harness. For premium/release UI or generated-asset work, prefer a harness unless determinism is a real blocker.
10b. Decide whether to run the bot playtest (
tests/bot-playtest.template.tsin scaffold games). For release-ready gameplay claims, run it and report the metrics JSON. - 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. Add --state <name> (and optionally --seed <n>) to drive the game's __THREE_GAME_TEST_HOOKS__ before capture, so every named state (active-play, fail, stress) can be measured deterministically without live play — outputs are suffixed per state. Generated games from the packaged scaffold also include their own scripts/inspect-threejs-canvas.mjs and npm run inspect:canvas.
The inspector JSON includes a metrics block (color entropy, edge density, luminance contrast, dominant-color share) and a renderBudget comparison against starting-point tier budgets. Cite these as the Measured Evidence in the visual scorecard (threejs-aaa-graphics-builder/references/visual-scorecard.md); over-budget rows need a documented tradeoff, and blank-canvas or error conditions still exit nonzero.
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. When visual baselines are in scope, include the harness decision, states covered, update/compare commands, artifact paths, thresholds/masks, and flake risks. When the bot playtest ran, include its metrics JSON (frames, score progression, distance, softlock windows, seed) and the added/extended/skipped decision.
Frequently asked questions about Three.js QA Release
Similar skills
Quality Playbook Generator
Run comprehensive quality audits on any codebase.
PR Draft Summary
Automate PR summary generation for openai-agents-python.
Final Release Review
Streamline your release candidate audits with ease.
Unit Test Vue Pinia
Efficiently write and review unit tests for Vue 3 applications.
Slang Shader Expert
Optimize and integrate Slang shaders with ease.
Telemetry Standards
Ensure consistent event tracking in Supabase Studio.