threejs-qa-release
Skill0 starsChanged 5 months agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- majidmanzarpour/threejs-game-skillstheir own version, first seen Sep 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- majidmanzarpour/threejs-game-skills★ 2.2ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- threejs-3d-generatorSkill
- threejs-aaa-graphics-builderSkill
- threejs-audio-generatorSkill
- threejs-debug-profilerSkill
- threejs-game-directorSkill
- threejs-gameplay-systemsSkill
- threejs-game-ui-designerSkill
- threejs-image-generatorSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Start dev or preview server.
- Distinctive: line 23
Verify nonblank canvas pixels.
- Distinctive: line 26
Check HUD text fit, safe areas, touch targets, responsive layout.
- Distinctive: line 27
If audio changed, verify user-gesture unlock, SFX triggers, ambience loop start/stop, pause/restart cleanup, mute/volume behavior, and …
- Distinctive: line 32
Use the bundled inspector when the target project does not already include one:
- Distinctive: line 44
Run production build and preview/static server.
- Distinctive: line 45
Verify built output desktop/mobile.
- Distinctive: line 47
Document deploy command, host assumptions, and residual risks.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:5188For 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

