agentsclimarketplace

Threejs qa release

Skill Oliyflemishspeaking560/threejs-game-skills/skills/threejs-qa-release

Build browser games with automated Three.js skills for Codex and Claude Code to manage graphics, logic, assets, and builds.

Install
npx -y skills add Oliyflemishspeaking560/threejs-game-skills --skill threejs-qa-release

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.6 KB, as published. Nobody here has run it

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.

  1. Install dependencies if needed.
  2. Run build/typecheck.
  3. Start dev or preview server.
  4. Open browser target.
  5. Capture console/page/network errors.
  6. Verify nonblank canvas pixels.
  7. Capture desktop and mobile screenshots.
  8. Trigger main input, objective progression, fail/retry, and recent risky paths.
  9. Check HUD text fit, safe areas, touch targets, responsive layout.
  10. If audio changed, verify user-gesture unlock, SFX triggers, ambience loop start/stop, pause/restart cleanup, mute/volume behavior, and decode/load errors.
  11. 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

  1. Inspect package scripts, Vite config, base path, public/assets.
  2. Gate debug UI/logging/test helpers.
  3. Run production build and preview/static server.
  4. Verify built output desktop/mobile.
  5. Review bundle and large assets.
  6. 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.