Threejs Qa Release logo

Threejs Qa Release

Organization
mintdotgg
threejs-qa-release

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.

Overview

Publishermintdotgg
Repositorymint-threejs-skills
Skill namethreejs-qa-release
Stars
125
Forks
11
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by mintdotgg on GitHub. Read the source before you install it.

Installation

Install the Threejs Qa Release AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/mintdotgg/mint-threejs-skills/tree/main/skills/mint-threejs-skills/skills/threejs-qa-release
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mintdotgg/mint-threejs-skills.git /tmp/mint-threejs-skills
mkdir -p .claude/skills
cp -r /tmp/mint-threejs-skills/skills/mint-threejs-skills/skills/threejs-qa-release .claude/skills/threejs-qa-release
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Threejs Qa Release in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Threejs Qa Release on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Threejs Qa Release is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

  1. Confirm the approved scope, then start the intended dev or production preview.
  2. Capture console, page, and relevant network errors.
  3. Verify nonblank canvas pixels and the approved active desktop view.
  4. Exercise the primary user journey and changed risky paths.
  5. Test loading, empty, unsupported, and error states when applicable.
  6. Check desktop UI fit, input cancellation, and resize.
  7. If audio changed, verify gesture unlock, decode/load, triggers, loops, cleanup, mute, and volume.
  8. Add deterministic screenshot baselines only when separately approved; otherwise record that they were not run.
  9. Run canvas diagnostics, profiling, production-preview checks, or game bot playtests only when the user approved those checks.
  10. 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:

bash
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

  1. Inspect scripts, Vite base, public assets, and deployment assumptions.
  2. Gate debug UI, verbose logging, and test helpers.
  3. Run production build and preview.
  4. Recheck desktop/mobile interaction and asset paths in built output.
  5. Review bundle size, large assets, and third-party asset notices.
  6. 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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Threejs Qa Release AI skill do?

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.

Why use Threejs Qa Release on TypingMind?

Because you install it once and use it with any model. Threejs Qa Release is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Threejs Qa Release in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mintdotgg/mint-threejs-skills/tree/main/skills/mint-threejs-skills/skills/threejs-qa-release. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Threejs Qa Release?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Threejs Qa Release?

As many as you like. As long as a model supports skills, you can use Threejs Qa Release with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Threejs Qa Release AI skill free?

Yes. It is published on GitHub by mintdotgg under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇