agentleFS
Oliyflemishspeaking560Oliyflemishspeaking560/threejs-game-skills/skills/threejs-qa-release/SKILL.md

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

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
  1. Distinctive:

    Start dev or preview server.

    line 20
  2. Distinctive:

    Verify nonblank canvas pixels.

    line 23
  3. Distinctive:

    Check HUD text fit, safe areas, touch targets, responsive layout.

    line 26
  4. Distinctive:

    If audio changed, verify user-gesture unlock, SFX triggers, ambience loop start/stop, pause/restart cleanup, mute/volume behavior, and …

    line 27
  5. Distinctive:

    Use the bundled inspector when the target project does not already include one:

    line 32
  6. Distinctive:

    Run production build and preview/static server.

    line 44
  7. Distinctive:

    Verify built output desktop/mobile.

    line 45
  8. Distinctive:

    Document deploy command, host assumptions, and residual risks.

    line 47

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.