Mint Three.js Skills

---
name: mint-threejs-skills
description: 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.
---

# 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