mint-threejs-skills

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Mint Three.js Skills

Mint Three.js 技能套件

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.

Mint专为基于浏览器的Three.js工作打造的Agent技能套件。它整合并适配了开源Three.js游戏、应用和图形Agent工作流，在保留深度游戏工作流的同时，实现了3D应用的通用化。

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.

若需求为生成单个模型、动画模型、连贯的模型资源包、单个材质、材质包，或明确要求的Mint场景：请阅读
```
references/asset-viewer.md
```
，然后使用应用管理器。资源是核心产物，查看器则是用于检查和下载资源的外壳。
通用3D应用、查看器、配置器、模拟器、漫游系统、编辑器或交互式体验：请阅读
```
skills/threejs-app-director/SKILL.md
```
。
包含目标、挑战、计分、失败机制、进度或游戏体验的游戏类需求：请阅读
```
skills/threejs-game-director/SKILL.md
```
。
混合体验需求：从应用管理器开始，仅添加相关的游戏专业模块。

两条路径共享视觉系统、交互逻辑、调试、QA以及

references/mint-mcp-assets.md

。在针对某个代码库首次调用Mint MCP写入资源前，请阅读

references/mint-project-workspaces.md

，为该工作确定一个Mint项目。使用Mint资源的项目还需遵循

references/asset-pipeline.md

中的持久化注册表规范。

现有应用或游戏上下文优先级高于资源交付。请将请求的资源生成并集成到现有项目中，而非搭建独立的查看器。

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.

现有项目架构优先级最高。对于全新项目，默认使用TypeScript、Vite和Three.js模块。
默认使用原生Three.js；当项目或用户指定时，支持React Three Fiber或其他基于Three.js的技术栈。
Mint MCP是唯一的生成资产生产管道。请勿在浏览器运行时代码中加入MCP调用。
区分本地代码项目（正在编辑的文件夹或仓库）与其对应的Mint项目（拥有Mint对话和资源的远程工作区）。仅需确定或创建一次Mint项目，将其持久化存储在
```
mint-assets.json
```
中，并在针对该代码库启动的每个独立生成任务中复用。
对于所有导入Mint文件或远程场景配置的项目，通过
```
scripts/sync-mint-assets.mjs
```
维护项目根目录下的
```
mint-assets.json
```
。复用稳定的逻辑键，并遵循现有项目的资源根目录约定。
对于所有加载Mint生成的GLB文件的Three.js路径，请阅读
```
references/gltf-runtime-compatibility.md
```
并使用支持Draco的共享加载器。Mint优化后的GLB文件与原生
```
GLTFLoader
```
不兼容。
优先选择独立生成的模型并在Three.js中进行组合。仅当用户明确选择生成环境时，才创建Mint场景；此时请阅读
```
references/mint-world-splats.md
```
。
当程序化资源或用户提供的资源更适合设计需求，或Mint MCP不具备所需能力时，优先使用此类资源。切勿为Mint已成功生成的对象创建竞争性的程序化版本。
在验证前，请阅读
```
references/verification-policy.md
```
。运行最低要求的自动验证，进行扩展桌面/浏览器QA前需征得同意，移动QA则需要单独的二次审批。其审批边界优先于更广泛的专业模块完成标准。
请勿将目标、压力、奖励或失败等游戏概念强加于通用3D应用。

User-Owned UI

用户自有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

将交付的应用视为用户的产品，而非资产生成管道的演示。
除非用户明确要求，否则请勿在运行时UI中加入供应商名称、品牌标识、徽章、生成链接、资源ID和来源信息。
仅在最终回复或开发者文档中提及生成来源和交接链接。
默认仅保留体验所需的最小UI：加载和错误状态、必要控件以及明确要求的操作。
除非用户要求，否则请勿添加页眉、标题栏、导航、营销文案、署名或装饰性应用框架。
对于标准资源查看器，保持画布的主导地位，搭配一个从信息按钮打开的紧凑居中详情对话框，以及底部居中的检查控件。请勿预留永久侧边栏空间。对于其他简单查看器和漫游系统，使用紧凑的底部居中控件组。使用相同的紧凑视觉语言，将加载、就绪或错误状态直接置于控件组上方。

当用户请求可复用的提示词时，请使用

references/request-templates.md

。