Mint Threejs Skills logo

Mint Threejs Skills

Organization
mintdotgg
mint-threejs-skills

Build, revise, debug, and verify browser-based Three.js apps, games, asset viewers, model and asset-pack deliveries, material and material-pack deliveries, animated-model viewers, and explicitly requested Gaussian-splat worlds with Mint MCP as the production asset pipeline.

Overview

Publishermintdotgg
Repositorymint-threejs-skills
Skill namemint-threejs-skills
Stars
125
Forks
11
Bundled files
79
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.

  • 79 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 Mint Threejs Skills 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
  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 .claude/skills/mint-threejs-skills
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mint Threejs Skills 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 Mint Threejs Skills 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 Mint Threejs Skills 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.

Mint Three.js Skills

Mint's agent skill suite for browser-based Three.js work. It combines and adapts open source Three.js game, application, and graphics-agent workflows, generalized for 3D apps while retaining deep game workflows.

Choose A Route

  • Fresh request whose primary deliverable is one generated model, an animated model, a coherent model asset pack, one material, a material pack, or one explicitly requested Mint world: read references/asset-viewer.md, then use the app director. The asset is the product; the viewer is its inspection and download shell.
  • General 3D app, viewer, configurator, simulation, walkthrough, editor, or interactive experience: read skills/threejs-app-director/SKILL.md.
  • Game or game-like request with objectives, challenge, scoring, failure, progression, or game feel: read skills/threejs-game-director/SKILL.md.
  • Mixed experience: start with the app director, then add only the relevant game specialists.

Both routes share visual systems, interaction, debugging, QA, and references/mint-mcp-assets.md. Before the first Mint MCP write for a codebase, read references/mint-project-workspaces.md to resolve one Mint Project for the work. Projects that use Mint assets also use the durable registry in references/asset-pipeline.md.

Existing app or game context wins over asset delivery. Generate and integrate a requested asset into that project instead of scaffolding a separate viewer.

Invariants

  • Existing project architecture wins. For greenfield work, default to TypeScript, Vite, and Three.js modules.
  • Vanilla Three.js is the default; support React Three Fiber or another Three.js-based stack when the project or user chooses it.
  • Mint MCP is the only generated-asset production pipeline. Keep MCP calls out of browser runtime code.
  • Distinguish the local code project (the folder or repository being edited) from its Mint Project (the remote workspace that owns Mint chats and assets). Resolve or create the Mint Project once, persist it in mint-assets.json, and reuse it for every independent generation started for that codebase.
  • For every project that imports Mint files or remote world configuration, maintain a project-root mint-assets.json through scripts/sync-mint-assets.mjs. Reuse stable logical keys and preserve the existing project's asset-root conventions.
  • For every Three.js path that loads Mint-generated GLBs, read references/gltf-runtime-compatibility.md and use a Draco-capable shared loader. Mint-optimized GLBs are not compatible with a bare GLTFLoader.
  • Prefer discrete generated models and compose them in Three.js. Generate a Mint world only when the user explicitly chooses a generated environment; then read references/mint-world-splats.md.
  • Use procedural or user-provided assets when they are the right design choice or Mint MCP lacks the required capability. Never create a competing procedural version of a subject that Mint generated successfully.
  • Before verification, read references/verification-policy.md. Run its automatic minimum, ask before extended desktop/browser QA, and require a separate secondary approval for mobile QA. Its approval boundary overrides broader specialist completion gates.
  • Do not force game concepts such as objectives, pressure, rewards, or failure onto general 3D apps.

User-Owned UI

  • Treat the delivered app as the user's product, not as a demo of the asset-generation pipeline.
  • Keep provider names, branding, badges, generation links, asset IDs, and provenance out of runtime UI unless the user explicitly asks for them.
  • Mention generation provenance and handoff links only in the final response or developer documentation.
  • Default to the minimum UI required for the experience: loading and error status, essential controls, and explicitly requested actions.
  • Do not add headers, title bars, navigation, marketing copy, attribution, or decorative application chrome unless requested.
  • For the canonical asset viewer, keep the canvas dominant with a compact centered details dialog opened from an info button plus bottom-centered inspection controls. Do not reserve permanent sidebar space. For other simple viewers and walkthroughs, use a compact bottom-centered control group. Place loading, ready, or error status directly above it using the same compact visual language.

When the user asks for a reusable prompt, use references/request-templates.md.

Bundled files

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

and 19 more files.

Frequently asked questions

What does the Mint Threejs Skills AI skill do?

Build, revise, debug, and verify browser-based Three.js apps, games, asset viewers, model and asset-pack deliveries, material and material-pack deliveries, animated-model viewers, and explicitly requested Gaussian-splat worlds with Mint MCP as the production asset pipeline.

Why use Mint Threejs Skills on TypingMind?

Because you install it once and use it with any model. Mint Threejs Skills 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 Mint Threejs Skills 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. 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 Mint Threejs Skills?

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 Mint Threejs Skills?

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

Is the Mint Threejs Skills 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 👇