evomeme 0.1.9 → 0.1.10-beta.13

package/dist/skills/zh-CN/phaser-2d-graphics-builder/references/visual-scorecard.md

@@ -0,0 +1,129 @@
+# Visual Scorecard (Phaser 2D)
+
+Score active-play screenshots, not idle title screens or isolated asset sheets. Prefer **mobile portrait** screenshots; add desktop when the project targets it.
+
+Scores are self-assessed against the anchors below, so they drift optimistic. For premium/showcase claims: cite Measured Evidence where possible, run the Fresh-Eyes Review, and compare against packaged anchors before finalizing.
+
+## Calibration Anchors
+
+Reference screenshots for score calibration are packaged in `phaser-2d-graphics-builder/assets/scorecard-anchors/`:
+
+- `scene-1.jpeg` — score ~1: geometric/simple hero and props on a flat sparse stage, utility HUD.
+- `scene-2.jpeg` — score ~2: authored sprites and scene art, readable state HUD, intentional composition; still short of dense active-play showcase.
+- `scene-3.jpg` — score ~2.5–3: dense layered authored world in active play, varied character family, readable state feedback, cohesive HUD.
+
+Before scoring World/environment, Hero/player, Sprite fidelity, Compose, or VFX, **view the anchors** and compare: if your screenshot reads closer to `scene-1.jpeg` than `scene-3.jpg` for that surface, the category is at most a 1–2 regardless of how much code was written.
+
+Do not score against title screens, collages, or marketing montages.
+
+## Scoring Scale
+
+- 0: Placeholder. Flat colors, missing art, unreadable state, debug UI, or no evidence.
+- 1: Basic styled. Playable and themed, but obvious prototype assets, flat composition, or generic UI.
+- 2: Premium stylized. Authored silhouettes, layered world, readable state, cohesive UI/world, measured performance.
+- 3: Showcase. Strong art direction, memorable hero and world, dense authored detail, excellent readability, polished VFX, diagnostics.
+
+## Categories
+
+1. Art direction.
+   - 0: No clear theme.
+   - 1: Theme is mostly a palette swap.
+   - 2: Theme affects sprites, world layers, UI, and feedback.
+   - 3: Distinct identity on every production surface.
+2. Hero/player.
+   - 0: Colored rectangle / emoji / default shape.
+   - 1: Basic sprite with glow or simple tint.
+   - 2: Authored silhouette, clear facing, state cues (hurt/boost).
+   - 3: Memorable sprite language with expressive feedback.
+3. Obstacles/enemies.
+   - 0: Same box as everything else.
+   - 1: Recolored repeated silhouette.
+   - 2: At least three readable variants with telegraphs.
+   - 3: Varied family with anticipation and gameplay clarity.
+4. Rewards/interactables.
+   - 0: Plain circle/token.
+   - 1: Repeated icon with simple pulse.
+   - 2: Two authored forms with idle/collect states.
+   - 3: Desirable, animated, clearly valued in motion.
+5. World/environment.
+   - 0: Flat fill or empty stage.
+   - 1: Single background image, sparse props.
+   - 2: Layered Play/Near/Mid/Far matching `scene-profiles` profile.
+   - 3: Dense authored world that still preserves play readability.
+6. Sprite fidelity / atlas.
+   - 0: Procedural shapes only.
+   - 1: Mixed placeholder + one real image.
+   - 2: Key surfaces from MCP/user art; consistent PPI and facing; sheets measured before load.
+   - 3: Cohesive atlas/mip strategy, clean cutouts, no stretched mush.
+7. Compose (camera / parallax / tint).
+   - 0: No depth; camera fights the player.
+   - 1: Parallax or tint used as the whole style.
+   - 2: Intentional camera, parallax ratios, depth sort, readable overlays.
+   - 3: Cinematic but disciplined compose; never hides the next decision.
+8. VFX/motion.
+   - 0: None or random ambient particles.
+   - 1: Generic particles/trails.
+   - 2: Event-driven FX for hit, pickup, fail, combo, spawn, dash.
+   - 3: High-impact FX that clarify state and stay within budget.
+9. UI/HUD.
+   - 0: Debug text or missing UI.
+   - 1: Generic stat cards over the canvas.
+   - 2: Genre HUD via DOM overlay; colors echo world signals.
+   - 3: Cohesive hierarchy and polished transitions without covering Play.
+10. Performance evidence.
+   - 0: No notes after visual changes.
+   - 1: Informal "seems fine".
+   - 2: Texture/display/particle budget notes + mobile screenshot.
+   - 3: Before/after or budget-aware notes, pooling, atlas strategy.
+
+## Thresholds
+
+Premium:
+
+- Every category at least 2.
+- Average at least 2.3.
+- Mobile active-play screenshot when portrait mobile is in scope.
+- Technical-art / budget notes after graphics changes.
+
+Showcase:
+
+- At least six categories score 3.
+- No category below 2.
+- Average at least 2.7.
+- Performance evidence includes before/after or budget-aware notes.
+
+## Automatic Failures
+
+Any of these prevents a premium/showcase claim:
+
+- Active screenshot is placeholder-dominant (SVG/rect/emoji as hero or main threats).
+- Main world is a flat fill with no authored Far/Mid layers when the profile requires them.
+- Hero is mostly a shape plus glow/particles.
+- Obstacles or rewards are one repeated silhouette recolored.
+- Ambient particles or full-screen flash are the primary “art”.
+- Compose (shake/vignette/parallax) hides the next gameplay decision.
+- Dense formal HUD drawn in Canvas instead of DOM without an explicit project requirement.
+- No asset sourcing ledger for premium hero/background surfaces.
+- Claimed premium while required references were skipped.
+
+## Fresh-Eyes Review
+
+Before finalizing premium/showcase:
+
+1. Look only at the latest active-play screenshot for 10 seconds.
+2. Name the weakest two categories without reading the scorecard you just filled.
+3. If either is below 2, lower scores and keep working—or report blockers.
+4. Confirm Automatic Failures are absent.
+
+## Measured Evidence
+
+Prefer citing:
+
+- `public/config.json` keys bound for hero/bg/parallax.
+- Screenshot paths (mobile/desktop).
+- Texture sizes / atlas notes / particle max counts from the technical art brief.
+- Phaser Scale mode confirmation (no CSS canvas scale).
+
+## Output
+
+When claiming premium/showcase, paste a filled table: category, score 0–3, one-line evidence, measured evidence if any. Include average and list Automatic Failures remaining (or “none”).

package/{skills → dist/skills/zh-CN}/threejs-3d-game/SKILL.md

@@ -25,8 +25,12 @@ description: 用 Three.js、React Three Fiber、TypeScript 与 Vite 实现 3D
 3. **纯 Three 模块可单测**
    - `game/three/*` 禁止 import React；场景构建与数学助手可独立验证。
 
-4. **资产键稳定**
-   - 全部游戏代码通过 `manifest` / `public/config.json` 引用资产，不在业务代码中硬编码 glTF / 贴图路径。
+4. **资产键稳定 + Canonical 语义**
+   - 全部游戏代码通过 `manifest` / `public/config.json` / canonical 包引用资产，不在业务代码中硬编码 glTF / 贴图路径。
+   - **3D 网格必须来自** `assets/canonical/<id>/`（或 `evomeme asset sync <id> --target three_js --project "<project>" --workspace "<workspace>" --json` 同步到 `public/assets/canonical/<id>/`）。
+   - 加载后**必须**按 `asset.json` 应用朝向/尺度（见 `references/engine-asset-pipeline.md`）；禁止在实体里硬编码 `rotation.y += Math.PI`。
+   - 对齐与预览默认走 `game-asset-align` + CLI `evomeme stage --asset <id> --target three_js`。先读 [CLI 契约](../game-asset-align/references/tool-contract.md)：`evomeme` 为 `npx -y evomeme@latest` 或同版本本地构建的简写；指定 `--workspace`，自动化加 `--json`。Stage 保持前台会话运行，拿到 URL 即交给用户，后续命令在另一终端执行。
+   - **Blender 建模或修改后必须先打开 Stage，由用户查看并确认当前 Three.js 版本后才能导入。** `alignment.ready=true` 或 `asset align` 不代替用户确认；不得手工复制或替用户点击绕过门禁。
 
 ## 实现指导
 

package/dist/skills/zh-CN/threejs-3d-game/references/engine-asset-pipeline.md

@@ -0,0 +1,155 @@
+# 引擎：资产加载与动画管线
+
+关注 **运行时如何安全接入 GLB**，以及如何消费 **canonical 资产包**（`model.glb` + `asset.json`）。
+
+加载/绑定网格、AnimationMixer、根运动、碰撞代理、导入后性能时加载本文件。路径与 config 契约仍以 `file-structure.md` 为准。对齐流程见技能 `game-asset-align`。
+
+命令中的 `evomeme` 按 [CLI 契约](../../game-asset-align/references/tool-contract.md) 选择启动方式；显式指定工作区。Stage 必须保持前台会话运行，后续 sync 在另一终端执行。
+
+## Canonical 包（强制）
+
+**Blender 建模/修改后必须先打开 Stage 展板。用户查看并点击“确认当前版本，允许导入”后，才可进行下一步导入。** `evomeme stage --asset <id> --workspace "<workspace>" --target three_js --json`；格式检查和 `alignment.ready` 只表示技术状态，不能跳过确认。修改模型、纹理、灯光或显示配置后旧确认失效，必须重新查看确认。
+
+Tripo / 代码建模 / Blender / 上传的模型，进游戏前必须是：
+
+```text
+assets/canonical/<asset_id>/model.glb
+assets/canonical/<asset_id>/asset.json
+```
+
+同步进 Vite 工程：
+
+```text
+evomeme asset sync <id> --target three_js --project "<project>" --workspace "<workspace>" --json
+→ public/assets/canonical/<asset_id>/
+```
+
+`asset.json` 关键字段：`forward_axis`、`scale_hint_metres`、`yaw/pitch/roll_offset_degrees`、`verified_by`。
+directional 资产（角色/枪械/载具）`verified_by` 不得为 `unverified`。
+
+运行时约定：**-Z forward，+Y up**（与 Godot 相同）。完整场景使用同步生成的 `src/evomeme-stage/<id>/canonical_loader.js`，调用 `loadReviewedScene`。它与 Stage 共用 scene-runtime.js 和 three-appearance.js，复现已确认的 PBR、灯光、环境、相机以及已有烘焙显示路径。项目须使用 Three.js **0.170.0**；版本不一致会报错，需统一依赖后重新查看。
+
+包内包含 three.appearance.json（已确认 profile、诊断与文件指纹）、THREE_IMPORT.md、锁定运行时和可独立查看的 three-preview.html。旧 applyCanonicalOrientation.ts 仅供旧模型代码兼容；它不负责完整场景显示。
+
+## 输出与加载偏好
+
+| 用途 | 格式 |
+| --- | --- |
+| Three 运行时 | 优先 GLB（PBR）+ 同目录 `asset.json` |
+| 动画交换 | FBX 按需，再谨慎导入或离线转 GLB |
+| 打印 / AR | STL/3MF、USDZ —— 非本游戏运行时默认 |
+
+- 用 `GLTFLoader`（`three/addons/loaders/GLTFLoader.js`）。
+- 运行时 URL：`./` 相对路径、`/assets/canonical/<id>/model.glb` 或外部 `http(s)`；禁止站点根随意绝对路径（见部署规则）。
+- 加载放在资产层 / `game/three` 助手，**不要**在实体每帧 update 里 `load`。
+- 业务代码通过 `manifest` / `config` / canonical `asset_id` 引用，不硬编码裸 URL。
+
+```ts
+import * as THREE from 'three';
+import { loadReviewedScene } from '../../evomeme-stage/courtyard/canonical_loader.js';
+
+// assetBase 来自部署资源配置，指向本场景目录并以 / 结尾。
+const runtime = await loadReviewedScene({
+  renderer, world: scene, camera, assetBase: config.assets.courtyard,
+});
+// 游戏主循环；由游戏负责更新相机画幅与 renderer 尺寸。
+runtime.render(camera, deltaSeconds);
+// 离场时
+runtime.dispose();
+```
+
+完整环境在一个 Scene 内只加载一次。道具使用 appearanceEnabled:false 接入已有环境，返回根节点已应用 canonical TRS，不得再套补偿旋转或缩放。返回值还有 animations 和 stats；玩法、物理、动画播放由游戏资产层接管。R3F 或自定义后处理需接管渲染循环并调用 runtime.render；仅让框架调用 renderer.render 会跳过完整场景烘焙/后处理路径。
+
+## 包装实体
+
+导入场景包进游戏实体时显式处理：
+
+- **必须**用 `asset.json` 统一 scale、pivot、朝向（外层 `Group`）
+- 包围盒 / 逻辑 bounds
+- **与视觉分离的 collision proxy**
+- 加载失败占位或错误态
+- 记录：文件大小、三角面、材质数、贴图尺寸、clip 名、`verified_by`
+
+## AnimationMixer
+
+```ts
+const mixer = new THREE.AnimationMixer(gltf.scene);
+const action = mixer.clipAction(gltf.animations[0]);
+action.play();
+
+// useFrame / 模拟后：秒
+mixer.update(deltaSeconds);
+```
+
+- 玩法状态映射到 clip：idle / walk-run / jump / attack / hurt / fall / turn 等。
+- 街机默认：**原地动画 + 代码位移**；若保留根运动，必须有意为之。
+- 重启时 stop actions、dispose mixer，避免叠播。
+
+## 根运动与导入动画注意（引擎侧）
+
+上游绑定/重定向的坑若存在，在引擎侧固定修法：
+
+1. 需要原地动画时优先在**导入后**处理，不要依赖不可控的上游 `animate_in_place` 行为。
+2. 原地化时只改顶层根骨位置轨（常见名 `Root.position`），且只钉死水平 XZ，**保留 Y**（跳跃起伏）。
+3. 不要广谱删 Hip/Pelvis 或 twist 轨：部分绑定把肢体蒙在 twist 上，删轨会塌肢体。
+
+```ts
+for (const clip of clips) {
+  for (const tr of clip.tracks) {
+    if (tr.name !== 'Root.position') continue;
+    const v = tr.values;
+    const x0 = v[0];
+    const z0 = v[2];
+    for (let i = 0; i < v.length; i += 3) {
+      v[i] = x0;
+      v[i + 2] = z0;
+    }
+  }
+}
+```
+
+批处理重定向若得到 `NlaTrack` / `NlaTrack.001`：按**请求顺序**用下标映射到预设名，加载后 `clip.name = 'walk'` 再按名选取。
+
+加载后打日志：`gltf.animations.map(c => \`${c.name} ${c.tracks.length} tracks\`)`。人型健康 clip 应驱动大量骨骼；只有极少 track 通常是上游绑定坏了，先修绑定。
+
+### FBX 摄入（人型重定向常见）
+
+- `FBXLoader` 依赖 `fflate`；bundler 一般自动带上。
+- 同一 take 可能出现两条不同 `|` 深度路径的 clip：**保留更浅**的那条。
+- 用关键词选 clip（walk / idle / attack），不要盲目 `animations[0]` 除非管线保证单 take。
+- FBX 常是 Phong，比 GLB PBR 暗；最终美术对齐可离线转 GLB。
+- 除「单根骨水平钉死」外，避免再在 loader 侧「修正」动画（易越修越坏）。
+
+## 性能纪律
+
+- 浏览器/移动：控面数、贴图尺寸；英雄件高质量 + 实例化/程序化配角。
+- Clone 时尽量共享 geometry/material。
+- 离场 / 换关 dispose 已加载资源。
+- 导入前后记 renderer diagnostics：calls、triangles、geometries、textures、materials、文件体积。
+- 运行时卡顿、池化、DPR、LOD 见 `engine-performance.md`。
+
+## 导入体检清单
+
+- [ ] 文件大小与三角面可接受
+- [ ] 网格 / 材质 / 贴图数量与尺寸
+- [ ] 当前灯光下 PBR 观感
+- [ ] 米制尺度与 pivot / bounds 来自 `asset.json`，非猜的
+- [ ] `verified_by` 已记录（directional 资产非 unverified）
+- [ ] 碰撞代理独立且调试可见
+- [ ] clip 名、时长、根运动策略明确
+- [ ] 失败有占位；成功路径进 manifest/config/canonical
+- [ ] 卸载与重开无泄漏
+- [ ] 未在玩法代码中硬编码补偿旋转
+
+## 常见修复
+
+| 问题 | 处理 |
+| --- | --- |
+| 过大/过小 | 外层 Group 归一化 bounds |
+| 朝向错 | **改 asset.json / 回展板**，不要在玩法 wrapper 里永久硬转 |
+| 尺度错 | 写 `scale_hint_metres` 后重新加载 |
+| 几何坏了 | Blender 修改并重新导出（原点/落地可用 `evomeme asset repair <id>`）→ Stage 重新确认 → sync |
+| 动画滑步/飘走 | 保留导出根运动后按上式只钉 XZ |
+| 太贵 | 降面、缩贴图、少唯一重模 |
+| 材质过暗/过亮 | 色域、tone mapping、环境光、曝光 |
+| 碰撞怪 | 视觉 mesh 不参与物理，另建 proxy |

package/{skills → dist/skills/zh-CN}/threejs-aaa-graphics-builder/SKILL.md

@@ -33,11 +33,11 @@ For broad "still looks basic", premium, AAA, high-fidelity, showcase, or less-ba
 
 External asset sourcing gate:
 
-- For premium/AAA/showcase/high-fidelity/less-basic graphics with a hero/player, character, creature, boss, vehicle, ship, building, weapon, signature prop, complex pickup, or hero environment piece, prefer authored procedural factories from `references/model-recipes.md` before settling for placeholders. Remote mesh generation is offline in the current release.
-- For concept needs, texture/material references, decals, logos, faction marks, icons, GUI art, skies, backgrounds, or title/menu art: prefer procedural/CSS/canvas UI art; use user-supplied local images via `evomeme_upload_game_asset`.
-- Create an asset sourcing ledger for each high-value surface: procedural / hybrid / user-provided, plus outputs or skip reason.
-- `not-needed` is valid only after the relevant path was considered and the ledger explains why external assets would not improve a non-hero support surface, or why an attempted MCP/CDN call shows a real blocker.
-- For premium hero surfaces, procedural-only is allowed; document that constraint and still meet silhouette/material/lighting quality via procedural authorship or user-provided GLB/FBX.
+- For premium/AAA/showcase/high-fidelity/less-basic graphics with a hero/player, character, creature, boss, vehicle, ship, building, weapon, signature prop, complex pickup, or hero environment piece, load `../game-asset-mesh-generator` before deciding procedural geometry is enough.
+- For concept needs, texture/material references, decals, logos, faction marks, icons, GUI art, skies, backgrounds, title/menu art, or image-to-3D inputs: prefer procedural/CSS/canvas UI art; use user-supplied local images via `evomeme_upload_game_asset` + MCP `evomeme_image_to_mesh`, or remote MCP `evomeme_generate_game_image` when available.
+- Create an asset sourcing ledger for each high-value surface: procedural / ../game-asset-mesh-generator / hybrid / user-provided, plus outputs or skip reason.
+- `not-needed` is valid only after the relevant path was considered and the ledger explains why external generation would not improve a non-hero support surface, or why an attempted MCP/CDN call shows a real blocker.
+- For premium hero surfaces, procedural-only is not an allowed final answer unless there is real blocker evidence. At least one high-value surface must show a 3D generator task ID, downloaded GLB/GLTF/FBX path, user-provided/remote 2D asset path, or documented hybrid chain.
 
 ## Workflow
 
@@ -45,7 +45,7 @@ External asset sourcing gate:
 2. Confirm or select a `scene_profile_id` from `../game-art/references/scene-profiles.md` (World / 3D · Lighting / Entities). If missing, write it before upgrading surfaces.
 3. Score visuals across art direction, hero/player, obstacles, rewards, world, materials, render, VFX, UI, and performance evidence.
 4. Add missing graphics architecture: material library, procedural textures/decals, model factories, world prop kit, technical-art budget, VFX system, render pipeline, diagnostics.
-5. Fill the external asset sourcing ledger per surface: procedural Three.js factory, user-provided model/2D reference, or a hybrid.
+5. Fill the external asset sourcing ledger per surface: procedural Three.js factory, user-provided/remote 2D reference, `../game-asset-mesh-generator` 3D generation, or a hybrid.
 6. Upgrade every weak visible surface, not only one hero object. World layers must match the chosen scene-profiles paradigm (Play / Near / Mid / Far / Motion).
 7. Add lighting/render/material polish after authored forms exist, following the paradigm's Lighting stack intent and `references/render-recipes.md`.
 8. Add event-driven VFX tied to gameplay state.

package/dist/skills/zh-CN/threejs-aaa-graphics-builder/references/checklists/aaa-game-quality-gate.md

@@ -0,0 +1,23 @@
+# AAA Browser Game Quality Gate
+
+- The game is immediately playable and not presented as a landing page.
+- The core loop has objective, scoring/progress, fail/retry, pacing, and feedback.
+- Screenshots do not read as a collection of default primitives, debug HUDs, or generic placeholder panels.
+- Unadorned boxes, cones, spheres, flat planes, and stretched buildings are not the dominant art language unless explicitly intentional.
+- UI is genre-specific, compact, readable during motion, responsive, and includes needed modal states.
+- Player, threats, rewards, and objectives have distinct silhouettes and material/feedback language.
+- Player/hero asset has primary silhouette, secondary structure, tertiary detail, material contrast, and state feedback.
+- Obstacle/enemy set includes at least three authored variants with unique telegraphs.
+- Reward/interactable set includes at least two authored variants with collection/interaction feedback.
+- World kit includes reusable modules and does not rely on one repeated skyline/block/road primitive.
+- The scene has foreground, midground, and background depth instead of one flat play lane.
+- Lighting, shadows, fog, and post-processing clarify depth and mood without hiding gameplay.
+- Procedural models use the authored factories, shared material kit, reusable prop kits, and collision proxies from `../implementation-blueprint.md` and `../technical-art.md`.
+- Movement, camera, speed, impact, and restart loop feel tuned through play, not just configured.
+- Audio/visual feedback exists for core actions and state transitions.
+- Mobile viewport preserves framing, safe areas, touch targets, and text fit.
+- Renderer diagnostics from `../technical-art.md` are reviewed when visual fidelity changes.
+- Visual scorecard in `../visual-scorecard.md` passes: every category at least 2 and average at least 2.3.
+- Build, browser run, console/page errors, screenshots, nonblank canvas, interaction, and responsive checks all pass.
+- A screenshot critique identifies no unresolved high-impact placeholder-quality blockers.
+- If any premium surface was intentionally deferred, the final report says which one and why.

package/dist/skills/zh-CN/threejs-aaa-graphics-builder/references/checklists/aaa-visual-scorecard.md

@@ -0,0 +1,19 @@
+# AAA Visual Scorecard Checklist
+
+Use with `../visual-scorecard.md`.
+
+- Current desktop and mobile active-play screenshots are available.
+- Art direction category scored 0-3.
+- Hero/player asset category scored 0-3.
+- Obstacles/enemies category scored 0-3.
+- Rewards/interactables category scored 0-3.
+- World/environment category scored 0-3.
+- Materials/textures category scored 0-3.
+- Lighting/render category scored 0-3.
+- VFX/motion category scored 0-3.
+- UI/HUD category scored 0-3.
+- Performance evidence category scored 0-3.
+- No automatic failure is present: check every item in the canonical Automatic Failures list in `../visual-scorecard.md` (do not rely on a from-memory summary of it).
+- Technical-art evidence includes material kit, VFX readability, instancing/LOD/culling decision, DPR/post/shadow tradeoffs, and imported asset diagnostics when generated/imported assets are used.
+- Premium gate passes only when every category is at least 2 and average score is at least 2.3.
+- Showcase gate passes only when at least six categories are 3, no category is below 2, and average score is at least 2.7.

package/dist/skills/zh-CN/threejs-aaa-graphics-builder/references/checklists/material-lighting-quality.md

@@ -0,0 +1,14 @@
+# Material and Lighting Quality Checklist
+
+Gate the lighting/material recipes in `../render-recipes.md` and the material kit in `../technical-art.md`.
+
+- Renderer color space, tone mapping, exposure, and shadow settings are intentional.
+- Key, fill, rim, ambient, and environment lighting follow the lighting stack in `../render-recipes.md` and clarify depth and gameplay roles.
+- Materials avoid flat default looks through roughness/metalness/emissive/vertex-color variation.
+- Important objects have readable silhouettes against background, fog, and effects.
+- Shadows help ground assets without obscuring navigation or collision boundaries.
+- Fog, bloom, particles, and post-processing support readability instead of hiding it.
+- Procedural textures or decals are scaled, stable, and not visually noisy during movement.
+- Materials reuse the shared kit in `../technical-art.md` where possible and are disposed when obsolete.
+- Desktop and mobile screenshots are checked after lighting/material changes.
+- Renderer info or frame-time evidence is gathered when render cost changes.

package/dist/skills/zh-CN/threejs-aaa-graphics-builder/references/checklists/performance-safe-visual-detail.md

@@ -0,0 +1,14 @@
+# Performance-Safe Visual Detail Checklist
+
+Gate the render budget and instancing/LOD guidance in `../technical-art.md`.
+
+- Baseline renderer info is captured when increasing fidelity.
+- Draw calls, triangles, geometries, materials, textures, and frame time are reviewed against the render budget in `../technical-art.md` after changes.
+- Repeated details use the instancing/LOD approach in `../technical-art.md`: instancing, shared resources, atlases, or generated texture reuse where practical.
+- High segment counts are limited to silhouette-critical forms.
+- Shadows are scoped by light count, shadow map size, casters/receivers, and camera distance.
+- Post-processing is justified by gameplay readability or strong art direction.
+- DPR caps or adaptive quality are considered for mobile.
+- Generated resources have a disposal/reuse strategy.
+- The worst-case gameplay scene, not only idle view, is inspected.
+- Visual detail remains readable at mobile resolution without excessive GPU cost.

package/dist/skills/zh-CN/threejs-aaa-graphics-builder/references/checklists/procedural-model-quality.md

@@ -0,0 +1,15 @@
+# Procedural Model Quality Checklist
+
+Gate the procedural modeling guidance in `../model-recipes.md` and the material kit in `../technical-art.md`.
+
+- The model has a recognizable silhouette from the gameplay camera.
+- Primary forms read clearly before material or post-processing detail.
+- Secondary detail supports the asset role: panels, trims, ridges, tubes, fins, sockets, decals, or emissive accents.
+- Tertiary detail is visible at intended camera distance and does not create noise.
+- Materials use the kit in `../technical-art.md` with purposeful contrast in roughness, metalness, color, emissive, or texture.
+- Bevels, curves, and segment counts improve silhouette or highlight behavior.
+- Repeated props use shared geometries/materials, instancing, or pools when practical.
+- Visual mesh and gameplay collision/proxy are intentionally separated when needed.
+- The factory returns named groups/meshes and keeps ownership/disposal clear.
+- Renderer diagnostics from `../technical-art.md` are checked when triangles, materials, textures, or draw calls increase.
+- Mobile screenshot still shows the asset as more than a primitive placeholder.

package/dist/skills/zh-CN/threejs-aaa-graphics-builder/references/checklists/technical-art-quality.md

@@ -0,0 +1,17 @@
+# Technical Art Quality Checklist
+
+Use before claiming premium, AAA, showcase, high-fidelity, or less-basic visual quality after graphics changes. Each item gates the guidance in `../technical-art.md`.
+
+- Technical art brief converts art direction into shapes, material roles, lighting, VFX, camera, UI/world motifs, and budgets.
+- Hero surfaces and support surfaces are identified separately.
+- Material kit uses the named shared roles from `../technical-art.md`, not scattered one-off colors/materials.
+- Shader/post-processing choices have player-facing purpose and measured or bounded cost.
+- VFX follow the event-driven language in `../technical-art.md`: readable, short-lived, and not hiding collision, threats, rewards, or UI.
+- Instancing is used for large repeated same-geometry/same-material detail where appropriate.
+- LOD, culling, or simplified far variants are planned for heavy background/imported assets.
+- Imported/generated models have scale, pivot/orientation, bounds, file size, triangle/material/texture counts when available, and collision proxies checked.
+- Decals/trim/detail systems reinforce function, route, faction, scale, or state.
+- Threats, rewards, interactables, and player state are not communicated by color alone.
+- DPR cap, shadow settings, post-processing passes, and mobile tradeoffs are reported.
+- Renderer diagnostics match the render budget reporting in `../technical-art.md`: calls, triangles, geometries, textures, and material count when available.
+- Final visual scorecard performance evidence category includes budget and technical-art evidence, not only screenshots.