evomeme 0.1.9 → 0.1.10

package/dist/skills/zh-CN/phaser-2d-graphics-builder/references/implementation-blueprint.md

@@ -0,0 +1,82 @@
+# Phaser 2D Graphics Implementation Blueprint
+
+Use when a Phaser game reads as basic even after it is playable. Goal: a production graphics architecture that can be iterated, scored, and budgeted. For premium/showcase work, also load `technical-art.md`.
+
+## Recommended Ownership
+
+Directory layout follows `../phaser-2d-game/references/file-structure.md`. Keep **rules in Systems**, **sprites/FX in Scene or view helpers**. Suggested modules (names can merge in small games; concepts must stay separate):
+
+```text
+src/game/assets/manifest.ts          # or public/config.json bindings
+src/game/view/SpriteFactory.ts       # hero / hazard / reward creators
+src/game/view/WorldPropKit.ts        # repeated props, tileside dressing
+src/game/view/DepthLayers.ts         # Play/Near/Mid/Far/Motion constants
+src/game/view/ComposeRig.ts          # camera helpers, parallax, vignette/tint
+src/game/view/VfxSystem.ts           # event-driven FX (pooled)
+src/game/view/QualityDiagnostics.ts  # optional counters / debug overlays
+src/scenes/GameplayScene.ts          # wires systems → view; no rule ownership
+```
+
+Asset files live under `assets/` (`characters/`, `environment/`, `fx/`, …) with stable keys in `public/config.json`.
+
+## Hybrid Asset Pipeline
+
+Choose the asset path per surface:
+
+- **MCP image** (`game-asset-image-generator`): hero, enemies, signature props, backgrounds, parallax layers, tileset sheets when art quality matters.
+- **User-provided**: local/remote URLs the user supplies; still bind via `config.json`.
+- **Procedural / Phaser Graphics / shapes**: collision debug, temporary stubs, repeated micro-detail, telegraph shapes that must stay code-driven.
+- **Hybrid**: MCP base sprite + code tint/flash/outline for states; or tileset + prop kit overlays.
+
+For premium hero, main background, and primary hazard family: do not finish with procedural-only unless a real MCP/user blocker is recorded.
+
+## Production Surfaces
+
+A premium pass must touch every weak visible surface:
+
+- Hero/player: authored silhouette, facing aligned with art brief, hurt/invuln/boost cues.
+- Hazards/enemies: ≥3 distinct silhouettes when the genre has multiple threat types; telegraphs readable.
+- Rewards/interactables: ≥2 forms; idle + collect states.
+- World kit: Play / Near / Mid / Far / Motion matching `scene-profiles` profile; parallax ratios documented.
+- Sprite fidelity: consistent pixel density; spritesheets measured before `load.spritesheet` (`engine-spritesheets.md`).
+- Compose: camera model, depth sort, tint/overlay discipline (`compose-recipes.md`).
+- VFX: event-driven only (`vfx-recipes.md`); pooled.
+- UI/world cohesion: DOM HUD colors echo hazard/reward/safe signals—do not redesign HUD here beyond color token alignment; full HUD work is `game-ui`.
+- Diagnostics: budget notes, screenshots, scorecard.
+
+## Technical Art Contract
+
+Before broad implementation, write the brief from `technical-art.md`: hero vs support surfaces, texture/display/particle budgets, atlas plan, VFX caps, mobile first cuts.
+
+## Depth Layer Contract
+
+Map `scene-profiles` layers to Phaser depth (example—adjust per game, keep gaps):
+
+| Layer | Role | Typical depth |
+| --- | --- | --- |
+| Far | Background / sky | 0–100 |
+| Mid | Stage / buildings | 100–300 |
+| Play | Actors, hazards, rewards | 500–800 |
+| Near | Foreground occluders | 900–1000 |
+| Motion / VFX | Muzzle, impact, dashes | 1100–1200 |
+| Screen FX | Flash/vignette containers | 2000+ |
+
+Document the chosen map in `DepthLayers.ts`. Actors that need Y-sort stay within Play band.
+
+## State Feedback Without Fake AAA
+
+Prefer, in order:
+
+1. Swap frame / anim / attachment sprite.
+2. Controlled tint / flash (short).
+3. Scale squash-stretch tied to gameplay events.
+4. Camera punch / hitstop (from `game-feel`, scaled for readability).
+5. Particles/trails last.
+
+Never use permanent bloom-like overlays to hide missing art.
+
+## Wiring Rules
+
+- Scene reads System state and spawns/updates view objects; Systems do not import Phaser GameObjects if avoidable.
+- All runtime image URLs come from `config.json` / manifest—no scattered hardcoded CDN strings in multiple files.
+- Scale only via Phaser Scale Manager (`engine-runtime.md`).

package/dist/skills/zh-CN/phaser-2d-graphics-builder/references/sprite-recipes.md

@@ -0,0 +1,90 @@
+# Sprite Recipes (Phaser 2D)
+
+Use before upgrading hero, hazard, reward, or world prop visuals. Recipes describe **readable silhouettes and production intent**, not full illustration briefs. Generation details stay in `../game-asset-image-generator/`.
+
+## Shared Rules
+
+- One subject per asset key; facing must match gameplay (right-facing runners stay right-facing in art).
+- Keep a **collision proxy** simpler than the art (rectangle/circle); art can overhang slightly if the hitbox stays fair.
+- Family variants share a motif (helmet shape, horn, stripe) so players learn the cast.
+- Pixel density: characters readable at mobile play size; do not upscale tiny icons into heroes.
+- Prefer transparent Assets for actors; opaque Background for Far plates; Parallax layers with alpha for Mid/Near dressing.
+
+## Hero / Player
+
+**Must have**
+
+- Clear silhouette at thumbnail size.
+- Readable front/facing (or top-down orientation for `topdown_map` / `board_table`).
+- At least one state cue path: idle vs hurt vs power (frame, overlay, or tint—documented).
+
+**Avoid**
+
+- Symmetric blobs with no facing.
+- Oversized weapon that hides the body.
+- Relying on outline glow as the only identity.
+
+**Upgrade path**
+
+1. Lock style from `game-art` (+ advanced style if requested).
+2. MCP generate `asset_player` (and optional `asset_player_hurt` / atlas frames).
+3. Wire anim keys; verify facing vs movement code.
+4. Add attach points later (dust, muzzle) without reskinning the whole hero.
+
+## Hazards / Enemies
+
+**Must have**
+
+- ≥3 variants when the design has multiple threat roles (blocker / chaser / ranged)—or document why the genre is single-threat.
+- Telegraph: wind-up pose, color flash, or warning glyph **before** damage frames.
+- Shape language distinct from rewards.
+
+**Avoid**
+
+- One square, three hues.
+- Camouflage against Mid/Far that makes hits feel unfair.
+
+## Rewards / Interactables
+
+**Must have**
+
+- High contrast vs Play floor.
+- Idle motion subtle (bob/pulse ≤ subtle); collect burst is event FX.
+- Two forms when economy has tiers (coin vs gem, weapon vs heal).
+
+**Avoid**
+
+- Same shape as hazards.
+- Permanent screen-covering sparkle.
+
+## World Prop Kit
+
+Build a small kit, not one-off decorations:
+
+| Kit piece | Use |
+| --- | --- |
+| Edge marker | Lane/arena boundary readability |
+| Mid module | Repeatable building/cliff/hedge segment |
+| Far plate | Single strong skyline or stage back |
+| Near fringe | Grass, railing, table lip—occludes lightly |
+| Hazard stripe / safe glyph | Gameplay-readable floor language |
+
+Repeat with tint variants; do not MCP-generate 50 unique bushes.
+
+## Tilesets
+
+When using tilemaps (`engine-tilemaps.md`):
+
+- One visual language per biome.
+- Collision layer ≠ decorated layer.
+- Autotile/seam care: avoid noisy tiles that hide pickups.
+
+## Backgrounds & Parallax
+
+- Far: full-bleed Background, no characters/UI in the plate.
+- Mid/Near parallax: fewer focal subjects; leave Play cone clean per `scene-profiles`.
+- Scroll factors: Far `0.1–0.3`, Mid `0.4–0.7`, Near `1.0–1.15` (tune per game; document).
+
+## Checklist Hook
+
+Before scoring Sprite fidelity / Hero / Obstacles / Rewards, run `checklists/sprite-quality.md`.

package/dist/skills/zh-CN/phaser-2d-graphics-builder/references/technical-art.md

@@ -0,0 +1,67 @@
+# Technical Art For Phaser 2D Games
+
+Use before premium/showcase graphics work, atlas/texture strategy, particle/VFX systems, or any visual pass that could affect mobile performance.
+
+Technical art bridges art direction and real-time constraints. Goal: readable authored detail that survives active play on mid-tier phones—not maximum particle counts.
+
+## Technical Art Brief
+
+Before implementation, write:
+
+- Art direction in renderable terms: silhouettes, layers, compose, VFX language, camera.
+- Hero surfaces vs support surfaces.
+- Texture/atlas plan: max page size, shared atlases vs discrete images.
+- VFX caps: max concurrent emitters, particle lifespans, pool sizes.
+- Display list budget target (rough): dynamic objects in Play band.
+- Asset strategy per surface: mcp-image / user / procedural / hybrid.
+- Mobile first cuts: what to disable first if frame time slips (screen FX → Near props → Mid parallax detail → particle rate).
+
+## Budget Starting Points
+
+Starting contracts—not universal limits. Measure on device; document overruns.
+
+| Metric (worst active-play) | Mobile portrait target | Notes |
+| --- | --- | --- |
+| Unique textures (approx.) | ≤ 40–60 | Prefer atlases; huge unique BGs count heavy |
+| Max single texture edge | ≤ 2048 | Prefer 1024–2048 backgrounds; split if needed |
+| Concurrent particle emitters | ≤ 8 | Pool; hard-cap on spam events |
+| Particles alive (sum) | ≤ 300–500 | Lower on low-end; kill on scene sleep |
+| Dynamic GameObjects (Play) | keep pooled | No per-frame `new` for bullets/FX |
+| Camera shake stacking | 1 active profile | Don’t stack 3 shakes |
+| DPR / resolution | Scale Manager FIT/SHOW_ALL | Never CSS-scale canvas |
+
+Also follow `../phaser-2d-game/references/engine-performance.md` (pooling, culling, update budgets).
+
+## Texture And Atlas Discipline
+
+- Measure spritesheet frame size before loader config (`engine-spritesheets.md`).
+- Don’t pack unrelated PPI into one sheet if it forces wasteful padding—but do atlas frequent FX/UI icons when possible.
+- Prefer WebP/PNG with real alpha; avoid huge uncompressed photo BGs when a painted 1080×1920 plate suffices.
+- Destroy/unload textures on scene shutdown when switching biomes with large unique plates.
+
+## Particles And FX Cost
+
+- Event-driven only; no permanent full-screen ambient snow unless genre-critical and budgeted.
+- Pre-create emitters; `explode`/`quantity` bursts over long-running drip when possible.
+- Additive blending sparingly on mobile.
+- Tie FX lifetime to gameplay feedback windows (100–400ms for hits; longer only for celebrations).
+
+## Compose Cost
+
+- Parallax layers are textures too—3 strong layers beat 8 weak ones.
+- Full-screen overlay Images are cheap vs thousands of nodes; don’t simulate vignette with 200 sprites.
+- Lights (Phaser Lights Manager) are optional and costly—default to tint/overlay recipes first.
+
+## Diagnostics To Report
+
+After a graphics pass, report:
+
+- Which surfaces used MCP vs procedural.
+- Texture strategy (atlases / largest BG size).
+- Particle/emitter caps chosen.
+- Any deliberate budget overrun + why.
+- Mobile screenshot path(s).
+
+## Checklist Hook
+
+Run `checklists/technical-art-quality.md` and `checklists/performance-safe-visual-detail.md` before claiming Performance evidence ≥ 2.

package/dist/skills/zh-CN/phaser-2d-graphics-builder/references/vfx-recipes.md

@@ -0,0 +1,67 @@
+# VFX Recipes (Phaser 2D)
+
+Event-driven visual effects that clarify game state. Load only after sprites and compose are readable. Core rule still applies: FX never substitutes for authored art.
+
+Cross-link: hand-feel timing principles in `../game-designer/references/game-feel.md`; UI motion in `../game-art/references/animation-specs.md`. This file is **in-world / camera FX** for Phaser.
+
+## Principles
+
+1. **One trigger → one readable beat.** Prefer a single strong burst over layered noise.
+2. **Severity scale.** Pickup < hit < kill < fail/clear. Strongest events must still leave the next decision visible.
+3. **Pool everything.** No allocating emitters per bullet in `update`.
+4. **Sync with audio when present.** Same frame as SFX when `game-audio` is wired.
+5. **No ambient filler** to hide empty Far layers.
+
+## Recipe Table
+
+| Event | Primary FX | Duration | Notes |
+| --- | --- | --- | --- |
+| Light confirm (UI-adjacent in world) | Small scale pop + brief spark | 100–200ms | Keep off HUD DOM |
+| Pickup / coin | Radial burst (8–16 particles) + optional arc to HUD anchor | 200–350ms | High contrast; don’t blanket Play |
+| Hit (player) | White/red flash on sprite + tiny camera shake | 80–120ms | Invuln blink separate from flash |
+| Hit (enemy) | Impact ring or directional sparks + hitstop 1–2 frames | 100–180ms | Direction from attack vector |
+| Block / parry | Sharp spark + short freeze | 80–150ms | Distinct from hurt |
+| Dash / boost | Motion streaks or afterimage (2–3 ghosts) | During dash | Cap ghosts; fade quick |
+| Death / explode | Larger burst + brief screen flash ≤30% alpha | 300–500ms | Then remove clutter |
+| Spawn | Poof / ring expand | 200–300ms | Telegraph if hostile |
+| Charge telegraph | Pulse outline / growing warning glyph | Wind-up length | Must be readable before damage |
+| Zone warning | Edge vignette or floor decal pulse | While zone active | Center Play stays clear |
+| Combo / milestone | Short celebratory burst + optional zoom punch | 250–400ms | Don’t stack with death FX |
+| Fail / soft lock | Gray flash or desat pulse | 200ms | Not seizure-level strobe |
+
+## Implementation Notes (Phaser)
+
+- Prefer `this.add.particles` with preconfigured `ParticleEmitter` reused via pools, or a small `VfxSystem.burst(kind, x, y, dir?)` API.
+- Sprite flash: tween `setTintFill` / short `setAlpha` blink; clear tint on complete.
+- Afterimages: spawn faded copies at depth just below hero; auto-destroy.
+- Screen flash: camera-fixed Rectangle or Image at Screen FX depth; fade out; ignore input blocking.
+- Respect `technical-art.md` emitter and particle caps; on spam (machine-gun hits), coalesce to rate-limited bursts.
+
+## Anti-Patterns
+
+- Permanent floating dust as “atmosphere” when Far art is missing.
+- Full-screen rainbow particles on every tap.
+- Shake so strong platforms/hazards can’t be aimed at.
+- Additive glow soup that blows out silhouette edges.
+- FX that spawn without a gameplay event (pure decoration loops).
+
+## Severity Ladder (default)
+
+```text
+0  none
+1  sprite-only (tint/scale)
+2  local particles
+3  local particles + camera punch
+4  screen flash + particles + punch
+```
+
+Map events to ≤ one ladder step above the previous severity so players learn intensity.
+
+## Checklist
+
+Before scoring VFX/motion ≥ 2:
+
+- [ ] Every FX kind maps to a gameplay event
+- [ ] Caps documented in technical art brief
+- [ ] Mobile screenshot shows FX without hiding hazards
+- [ ] No ambient-only particle layer required for “premium”

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_to_three` 同步到 `public/assets/canonical/<id>/`）。
+   - 加载后**必须**按 `asset.json` 应用朝向/尺度（见 `references/engine-asset-pipeline.md`）；禁止在实体里硬编码 `rotation.y += Math.PI`。
+   - 对齐与预览默认走技能 `game-asset-align` + MCP `evomeme_stage_open`。
+   - **Blender 建模或修改后必须先打开 Stage，由用户查看并确认当前 Three.js 版本后才能导入。** `alignment.ready=true` 或 set_orientation 不代替用户确认；不得手工复制或替用户点击绕过门禁。
 
 ## 实现指导
 

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

@@ -1,39 +1,72 @@
 # 引擎：资产加载与动画管线
 
-关注 **运行时如何安全接入 GLB/FBX**。
+关注 **运行时如何安全接入 GLB**，以及如何消费 **canonical 资产包**（`model.glb` + `asset.json`）。
 
-加载/绑定网格、AnimationMixer、根运动、碰撞代理、导入后性能时加载本文件。路径与 config 契约仍以 `file-structure.md` 为准。
+加载/绑定网格、AnimationMixer、根运动、碰撞代理、导入后性能时加载本文件。路径与 config 契约仍以 `file-structure.md` 为准。对齐流程见技能 `game-asset-align`。
+
+## Canonical 包（强制）
+
+**Blender 建模/修改后必须先打开 Stage 展板。用户查看并点击“确认当前版本，允许导入”后，才可进行下一步导入。** `evomeme_stage_open({workspace_dir,asset_id,target:"three_js"})`；格式检查和 `alignment.ready` 只表示技术状态，不能跳过确认。修改模型、纹理、灯光或显示配置后旧确认失效，必须重新查看确认。
+
+Tripo / 代码建模 / Blender / 上传的模型，进游戏前必须是：
+
+```text
+assets/canonical/<asset_id>/model.glb
+assets/canonical/<asset_id>/asset.json
+```
+
+同步进 Vite 工程：
+
+```text
+evomeme_asset_sync_to_three
+→ 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） |
+| Three 运行时 | 优先 GLB（PBR）+ 同目录 `asset.json` |
 | 动画交换 | FBX 按需，再谨慎导入或离线转 GLB |
 | 打印 / AR | STL/3MF、USDZ —— 非本游戏运行时默认 |
 
 - 用 `GLTFLoader`（`three/addons/loaders/GLTFLoader.js`）。
-- 运行时 URL：`./` 相对路径或外部 `http(s)`；禁止站点根绝对路径 `/...`（见部署规则）。
+- 运行时 URL：`./` 相对路径、`/assets/canonical/<id>/model.glb` 或外部 `http(s)`；禁止站点根随意绝对路径（见部署规则）。
 - 加载放在资产层 / `game/three` 助手，**不要**在实体每帧 update 里 `load`。
-- 业务代码通过 `manifest` / `config` 键引用，不硬编码 URL。
+- 业务代码通过 `manifest` / `config` / canonical `asset_id` 引用，不硬编码裸 URL。
 
 ```ts
-import { GLTFLoader } from 'three/addons/loaders/GLTFLoader.js';
-
-const loader = new GLTFLoader();
-const gltf = await loader.loadAsync(urlFromManifest);
-wrapper.add(gltf.scene);
+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 会跳过完整场景烘焙/后处理路径。
+
 ## 包装实体
 
 导入场景包进游戏实体时显式处理：
 
-- 统一 scale、pivot、朝向（可外层 `Group`）
+- **必须**用 `asset.json` 统一 scale、pivot、朝向（外层 `Group`）
 - 包围盒 / 逻辑 bounds
 - **与视觉分离的 collision proxy**
 - 加载失败占位或错误态
-- 记录：文件大小、三角面、材质数、贴图尺寸、clip 名
+- 记录：文件大小、三角面、材质数、贴图尺寸、clip 名、`verified_by`
 
 ## AnimationMixer
 
@@ -98,18 +131,22 @@ for (const clip of clips) {
 - [ ] 文件大小与三角面可接受
 - [ ] 网格 / 材质 / 贴图数量与尺寸
 - [ ] 当前灯光下 PBR 观感
-- [ ] 米制尺度与 pivot / bounds
+- [ ] 米制尺度与 pivot / bounds 来自 `asset.json`，非猜的
+- [ ] `verified_by` 已记录（directional 资产非 unverified）
 - [ ] 碰撞代理独立且调试可见
 - [ ] clip 名、时长、根运动策略明确
-- [ ] 失败有占位；成功路径进 manifest/config
+- [ ] 失败有占位；成功路径进 manifest/config/canonical
 - [ ] 卸载与重开无泄漏
+- [ ] 未在玩法代码中硬编码补偿旋转
 
 ## 常见修复
 
 | 问题 | 处理 |
 | --- | --- |
 | 过大/过小 | 外层 Group 归一化 bounds |
-| 朝向错 | wrapper 旋转，或生成侧对齐选项 |
+| 朝向错 | **改 asset.json / 回展板**，不要在玩法 wrapper 里永久硬转 |
+| 尺度错 | 写 `scale_hint_metres` 后重新加载 |
+| 几何坏了 | `evomeme_asset_repair_blender` → 再展板对齐 → 再 sync |
 | 动画滑步/飘走 | 保留导出根运动后按上式只钉 XZ |
 | 太贵 | 降面、缩贴图、少唯一重模 |
 | 材质过暗/过亮 | 色域、tone mapping、环境光、曝光 |

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.