Back to Details

router

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Master Router — Game-Development Skill Dispatcher

主路由工具 — 游戏开发技能调度器

The entry point for game-development work. It fingerprints the project to pick one engine, classifies the task from the request, names the minimal set of specialized skills, and tells you to read them before acting. It dispatches and composes — it does not re-teach engine APIs.
游戏开发工作的入口。它会识别项目特征以选择一款引擎，根据请求分类任务，列出最少数量的专业技能，并告知你在执行前阅读这些技能。它的作用是调度与组合——不会重复教授引擎API。

When to use

使用场景

  • Use at the start of any game-development request — building or debugging a game, level, player, enemy, shader, UI, save system, multiplayer, input, audio, AI, dialogue, or procedural content — to decide which skill(s) to load.
  • Use when the user names an engine or genre, says "make a game", or asks "which skill should I use?".
When not to use: once the right skill is loaded and the task is squarely inside it, work from that skill — don't re-run the router every turn. Re-route only when the task pivots to a new engine or concern (router step 6).
  • 在任何游戏开发请求的起始阶段使用——无论是制作或调试游戏、关卡、玩家、敌人、着色器、UI、存档系统、多人联机、输入、音频、AI、对话还是程序化内容——以确定应加载哪些技能。
  • 当用户指定引擎或游戏类型、提出“制作一款游戏”或询问“我应该使用哪种技能？”时使用。
不适用场景： 当正确的技能已加载且任务完全属于该技能范畴时，直接基于该技能开展工作——无需每次都重新运行路由工具。仅当任务转向新引擎或新关注点时，才重新进行路由（见路由算法第6步）。

Routing algorithm

路由算法

  1. Detect engine — project fingerprint → at most one engine skill set (or "unknown"). §1.
  2. Classify task — phrasing → discipline(s) + at most one genre + workflow(s). §2.
  3. Resolve — the minimal set: engine skill(s) + discipline(s) + genre + workflow(s). §3.
  4. Read (disclosure) — open only the chosen 
    SKILL.md
    bodies; 
    references/
    only on demand. §4.
  5. Compose — order: engine fundamentals → discipline concept → genre glue → workflow. §5.
  6. Fallback — engine unknown or no skill fits → ask or default to Godot; state any gap. §6.
  1. 引擎检测——识别项目特征 → 选择至多一套引擎技能（或标记为“未知”）。详见第1节。
  2. 任务分类——根据请求表述 → 确定专业领域（可多个）+ 至多一种游戏类型 + 工作流（可多个）。详见第2节。
  3. 技能解析——确定最少技能组合：引擎技能 + 专业领域技能 + 游戏类型技能 + 工作流技能。详见第3节。
  4. 阅读规则（渐进式披露）——仅打开选定的
    SKILL.md
    内容；仅在需要时才查看
    references/
    目录下的文件。详见第4节。
  5. 技能组合——顺序：引擎基础技能 → 专业领域概念技能 → 游戏类型整合技能 → 工作流技能。详见第5节。
  6. Fallback机制——若引擎未知或无匹配技能 → 询问用户或默认选用Godot；明确说明存在的技能缺口。详见第6节。

1. Engine detection (project fingerprint)

1. 引擎检测（项目特征识别）

Scan for the highest-confidence signal; choose exactly one engine. Stop at the first match.
#EnginePrimary signalSkill set root
1Godot
project.godot
skills/godot/
2Unreal
*.uproject
skills/unreal/
3Unity
Assets/
and 
ProjectSettings/ProjectVersion.txt
skills/unity/
4Bevy
Cargo.toml
with a 
bevy
dependency
skills/other-engines/bevy-ecs/
5Phaser
package.json
dep 
phaser
skills/web-engines/phaser-*
6PixiJS
package.json
dep 
pixi.js
skills/web-engines/pixijs-rendering/
7three.js
package.json
dep 
three
skills/web-engines/threejs-*
8LÖVE
conf.lua
/ 
main.lua
calling 
love.*
skills/other-engines/love2d-core/
9pygame
*.py
with 
import pygame
skills/other-engines/pygame-core/
10Roblox
*.rbxl(x)
/ 
*.project.json
(Rojo)
skills/other-engines/roblox-*
For secondary signals, the Godot-C#/Unity/Bevy and multi-web disambiguation rules, monorepos, and plain-text engine mentions, read 
references/engine-detection.md
.
扫描最具可信度的特征信号；仅选择一款引擎，找到第一个匹配项后即停止。
#EnginePrimary signalSkill set root
1Godot
project.godot
skills/godot/
2Unreal
*.uproject
skills/unreal/
3Unity
Assets/
and 
ProjectSettings/ProjectVersion.txt
skills/unity/
4Bevy
Cargo.toml
with a 
bevy
dependency
skills/other-engines/bevy-ecs/
5Phaser
package.json
dep 
phaser
skills/web-engines/phaser-*
6PixiJS
package.json
dep 
pixi.js
skills/web-engines/pixijs-rendering/
7three.js
package.json
dep 
three
skills/web-engines/threejs-*
8LÖVE
conf.lua
/ 
main.lua
calling 
love.*
skills/other-engines/love2d-core/
9pygame
*.py
with 
import pygame
skills/other-engines/pygame-core/
10Roblox
*.rbxl(x)
/ 
*.project.json
(Rojo)
skills/other-engines/roblox-*
关于次要特征信号、Godot-C#/Unity/Bevy的区分规则、多Web引擎的歧义消除、单仓项目以及纯文本提及的引擎信息，请查看
references/engine-detection.md
。

2. Task classification (phrasing → category)

2. 任务分类（请求表述 → 类别）

After the engine, read the request for task signals (three additive categories):
  • disciplines (cross-engine concepts): 
    game-ai
    , 
    procedural-gen
    , 
    dialogue-systems
    , 
    save-systems
    , 
    audio-design
    , 
    shader-programming
    , 
    physics-tuning
    , 
    level-design
    , 
    input-systems
    , 
    game-feel
    , 
    camera-systems
    , 
    game-ui-ux
    , 
    performance-optimization
    . Triggered by concept words ("pathfinding", "save slots", "fragment shader", "screen shake", "camera follow", "HUD/menu", "optimize/low FPS").
  • genres (whole-game templates): 
    platformer
    , 
    roguelike
    , 
    rpg
    , 
    fps-shooter
    , 
    tower-defense
    , 
    card-game
    , 
    visual-novel
    , 
    survival-crafting
    , 
    puzzle
    . Triggered by genre words ("make a roguelike", "deckbuilder").
  • workflows (process/shipping): 
    game-jam
    , 
    prototype-fast
    , 
    steam-publish
    , 
    itch-publish
    . Triggered by process words ("publish on Steam", "vertical slice").
File signals sharpen this: 
*.yarn
/
*.ink
→ 
dialogue-systems
/
visual-novel
; 
steam_appid.txt
→ 
steam-publish
; 
*.inputactions
→ 
unity-input-system
.
确定引擎后，从请求中识别任务信号（分为三个可叠加的类别）：
  • 专业领域（跨引擎概念）：
    game-ai
    、
    procedural-gen
    、
    dialogue-systems
    、
    save-systems
    、
    audio-design
    、
    shader-programming
    、
    physics-tuning
    、
    level-design
    、
    input-systems
    、
    game-feel
    、
    camera-systems
    、
    game-ui-ux
    、
    performance-optimization
    。由概念词汇触发（如“寻路”“存档槽”“片段着色器”“屏幕震动”“相机跟随”“HUD/菜单”“优化/低帧率”）。
  • 游戏类型（整游戏模板）：
    platformer
    、
    roguelike
    、
    rpg
    、
    fps-shooter
    、
    tower-defense
    、
    card-game
    、
    visual-novel
    、
    survival-crafting
    、
    puzzle
    。由类型词汇触发（如“制作一款肉鸽游戏”“卡组构建”）。
  • 工作流（流程/发布）：
    game-jam
    、
    prototype-fast
    、
    steam-publish
    、
    itch-publish
    。由流程词汇触发（如“在Steam发布”“垂直切片”）。
文件类型信号可进一步细化分类：
*.yarn
/
*.ink
文件对应 
dialogue-systems
/
visual-novel
；
steam_appid.txt
文件对应 
steam-publish
；
*.inputactions
文件对应 
unity-input-system
。

3. Routing table (task → category → skill)

3. 路由表（任务 → 类别 → 技能）

3a. Engine skills — read the one matching the detected engine + sub-task

3a. 引擎技能——读取与检测到的引擎及子任务匹配的技能

  • Godot (
    skills/godot/
    ): language 
    godot-gdscript
    / 
    godot-csharp
    ; structure 
    godot-nodes-scenes
    , 
    godot-signals-groups
    ; 2D 
    godot-2d-movement
    , 
    godot-tilemap
    ; 3D 
    godot-3d-essentials
    ; physics 
    godot-physics
    ; UI 
    godot-ui-control
    ; animation 
    godot-animation
    ; shaders 
    godot-shaders
    ; data 
    godot-resources
    ; audio 
    godot-audio
    ; netcode 
    godot-multiplayer
    ; ship 
    godot-export
    .
  • Unity (
    skills/unity/
    ): scripting 
    unity-csharp-scripting
    ; input 
    unity-input-system
    ; physics 
    unity-physics
    ; animation 
    unity-animation
    ; data 
    unity-scriptableobjects
    ; 2D 
    unity-tilemap-2d
    ; AI nav 
    unity-navmesh
    ; ship 
    unity-build-pipeline
    .
  • Unreal (
    skills/unreal/
    ): visual scripting 
    unreal-blueprints
    ; C++ gameplay 
    unreal-cpp-gameplay
    ; input 
    unreal-enhanced-input
    ; AI 
    unreal-behavior-trees
    ; VFX 
    unreal-niagara
    ; ship 
    unreal-packaging
    .
  • Web (
    skills/web-engines/
    ): 
    phaser-core
    , 
    phaser-arcade-physics
    ; 
    pixijs-rendering
    ; 
    threejs-scene-setup
    , 
    threejs-gltf-loading
    , 
    threejs-materials-lighting
    .
  • Other (
    skills/other-engines/
    ): 
    bevy-ecs
    , 
    pygame-core
    , 
    love2d-core
    , 
    roblox-luau
    , 
    roblox-datastores
    .
  • Godot（
    skills/godot/
    ）：语言类技能
    godot-gdscript
    /
    godot-csharp
    ；结构类技能
    godot-nodes-scenes
    、
    godot-signals-groups
    ；2D类技能
    godot-2d-movement
    、
    godot-tilemap
    ；3D类技能
    godot-3d-essentials
    ；物理类技能
    godot-physics
    ；UI类技能
    godot-ui-control
    ；动画类技能
    godot-animation
    ；着色器类技能
    godot-shaders
    ；数据类技能
    godot-resources
    ；音频类技能
    godot-audio
    ；网络编码类技能
    godot-multiplayer
    ；发布类技能
    godot-export
    。
  • Unity（
    skills/unity/
    ）：脚本类技能
    unity-csharp-scripting
    ；输入类技能
    unity-input-system
    ；物理类技能
    unity-physics
    ；动画类技能
    unity-animation
    ；数据类技能
    unity-scriptableobjects
    ；2D类技能
    unity-tilemap-2d
    ；AI导航类技能
    unity-navmesh
    ；发布类技能
    unity-build-pipeline
    。
  • Unreal（
    skills/unreal/
    ）：可视化脚本类技能
    unreal-blueprints
    ；C++游戏玩法类技能
    unreal-cpp-gameplay
    ；输入类技能
    unreal-enhanced-input
    ；AI类技能
    unreal-behavior-trees
    ；视觉特效类技能
    unreal-niagara
    ；打包发布类技能
    unreal-packaging
    。
  • Web引擎（
    skills/web-engines/
    ）：
    phaser-core
    、
    phaser-arcade-physics
    ；
    pixijs-rendering
    ；
    threejs-scene-setup
    、
    threejs-gltf-loading
    、
    threejs-materials-lighting
    。
  • 其他引擎（
    skills/other-engines/
    ）：
    bevy-ecs
    、
    pygame-core
    、
    love2d-core
    、
    roblox-luau
    、
    roblox-datastores
    。

3b. Disciplines — load with the engine skill (concept ↔ engine API)

3b. 专业领域技能——与引擎技能一同加载（概念 ↔ 引擎API）

Concept (
says:
)		Discipline skillPairs with (engine API)
enemy AI, behavior tree, pathfinding, steering
game-ai
unity-navmesh
/ 
unreal-behavior-trees
/ Godot nav
procedural, noise, seed, dungeon generator
procedural-gen
engine tilemap/grid skill
dialogue, Yarn, Ink, conversation tree
dialogue-systems
engine UI skill
save/load, slots, persistence
save-systems
roblox-datastores
/ engine IO
adaptive music, mixer, ducking, SFX
audio-design
godot-audio
/ Unity AudioMixer
shader, fragment, dissolve/outline
shader-programming
godot-shaders
/ engine material
jitter, tunneling, fixed timestep
physics-tuning
godot-physics
/ 
unity-physics
whitebox, blockout, tile layout, pacing
level-design
godot-tilemap
/ 
unity-tilemap-2d
rebind, gamepad, input buffering
input-systems
unity-input-system
/ 
unreal-enhanced-input
/ Godot InputMap
screen shake, hit-stop, juice, squash & stretch, "make it punchy"
game-feel
engine animation/tween + 
camera-systems
(shake)
camera follow, deadzone, look-ahead, orbit, first-person
camera-systems
godot-2d-movement
/ 
godot-3d-essentials
/ Cinemachine
HUD, menu, UI layout, scaling, safe area, focus nav
game-ui-ux
godot-ui-control
/ Unity UI (UGUI/UI Toolkit)
low FPS, optimize, draw calls, GC spike, pooling, profiler
performance-optimization
engine profiler + 
physics-tuning
概念（用户表述）专业领域技能搭配引擎API
敌人AI、行为树、寻路、转向
game-ai
unity-navmesh
/ 
unreal-behavior-trees
/ Godot导航系统
程序化、噪声、种子、地牢生成器
procedural-gen
引擎 tilemap/网格技能
对话、Yarn、Ink、对话树
dialogue-systems
引擎UI技能
存档/读档、存档槽、数据持久化
save-systems
roblox-datastores
/ 引擎IO系统
自适应音乐、混音器、闪避音效、特效音
audio-design
godot-audio
/ Unity AudioMixer
着色器、片段、溶解/轮廓效果
shader-programming
godot-shaders
/ 引擎材质系统
抖动、穿模、固定时间步长
physics-tuning
godot-physics
/ 
unity-physics
白盒、区块规划、tile布局、节奏把控
level-design
godot-tilemap
/ 
unity-tilemap-2d
按键重绑定、游戏手柄、输入缓冲
input-systems
unity-input-system
/ 
unreal-enhanced-input
/ Godot InputMap
屏幕震动、击中停顿、游戏手感、挤压拉伸、“让打击感更强烈”
game-feel
引擎动画/补间 + 
camera-systems
（震动效果）
相机跟随、死区、前瞻、环绕、第一人称
camera-systems
godot-2d-movement
/ 
godot-3d-essentials
/ Cinemachine
HUD、菜单、UI布局、缩放、安全区域、焦点导航
game-ui-ux
godot-ui-control
/ Unity UI（UGUI/UI Toolkit）
低帧率、优化、绘制调用、GC峰值、对象池、性能分析器
performance-optimization
引擎性能分析器 + 
physics-tuning

3c. Genres — compose engine + disciplines (bind 
*
to the detected engine)

3c. 游戏类型技能——组合引擎技能与专业领域技能（将
*
绑定到检测到的引擎）

Genre (
says:
)		composes
platformer, jump, double jump
godot-2d-movement
(or engine physics) + 
godot-tilemap
/
unity-tilemap-2d
+ 
level-design
+ 
camera-systems
+ 
game-feel
roguelike, procedural dungeon, permadeath
procedural-gen
+ 
godot-tilemap
/
unity-tilemap-2d
+ 
game-ai
+ 
save-systems
+ 
game-feel
RPG, stats, inventory, quests
godot-resources
/
unity-scriptableobjects
+ 
dialogue-systems
+ 
save-systems
+ 
game-ui-ux
FPS, first-person, hitscan
godot-3d-essentials
/
unreal-cpp-gameplay
+ 
input-systems
+ 
game-ai
+ 
camera-systems
+ 
game-feel
tower defense, waves, lanes
game-ai
+ engine movement + 
level-design
+ 
game-ui-ux
card game, deckbuilder, TCG
godot-resources
/
unity-scriptableobjects
+ 
game-ui-ux
(+ engine UI)
visual novel, branching story
dialogue-systems
+ 
save-systems
+ 
game-ui-ux
survival, crafting, gathering
save-systems
+ 
godot-resources
/
unity-scriptableobjects
+ 
procedural-gen
+ 
game-ui-ux
puzzle, match-3, grid logic
godot-tilemap
/
unity-tilemap-2d
+ 
level-design
+ 
game-feel
游戏类型（用户表述）技能组合
平台跳跃、跳跃、二段跳
godot-2d-movement
（或引擎物理技能） + 
godot-tilemap
/
unity-tilemap-2d
+ 
level-design
+ 
camera-systems
+ 
game-feel
肉鸽、程序化地牢、永久死亡
procedural-gen
+ 
godot-tilemap
/
unity-tilemap-2d
+ 
game-ai
+ 
save-systems
+ 
game-feel
RPG、属性、背包、任务
godot-resources
/
unity-scriptableobjects
+ 
dialogue-systems
+ 
save-systems
+ 
game-ui-ux
FPS、第一人称、射线检测
godot-3d-essentials
/
unreal-cpp-gameplay
+ 
input-systems
+ 
game-ai
+ 
camera-systems
+ 
game-feel
塔防、波次、路线
game-ai
+ 引擎移动技能 + 
level-design
+ 
game-ui-ux
卡牌游戏、卡组构建、集换式卡牌
godot-resources
/
unity-scriptableobjects
+ 
game-ui-ux
（+ 引擎UI技能）
视觉小说、分支剧情
dialogue-systems
+ 
save-systems
+ 
game-ui-ux
生存、制作、收集
save-systems
+ 
godot-resources
/
unity-scriptableobjects
+ 
procedural-gen
+ 
game-ui-ux
解谜、三消、网格逻辑
godot-tilemap
/
unity-tilemap-2d
+ 
level-design
+ 
game-feel

3d. Workflows — engine-independent process & shipping

3d. 工作流技能——独立于引擎的流程与发布技能

game-jam
(jam, 48-hour, Ludum Dare/GMTK) · 
prototype-fast
(vertical slice, MVP, greybox) · 
steam-publish
(Steam, Steamworks, depot; 
steam_appid.txt
) · 
itch-publish
(itch.io, butler; 
.itch.toml
).
For the exhaustive per-skill trigger list and every engine binding, read 
references/routing-table.md
.
game-jam
（Game Jam、48小时开发、Ludum Dare/GMTK）· 
prototype-fast
（垂直切片、MVP、灰盒原型）· 
steam-publish
（Steam、Steamworks、分发仓库；
steam_appid.txt
）· 
itch-publish
（itch.io、butler工具；
.itch.toml
）。
如需查看详尽的各技能触发词列表及所有引擎绑定规则，请查看
references/routing-table.md
。

4. Read protocol (progressive disclosure)

4. 阅读规则（渐进式披露）

  1. Preloaded: only each skill's 
    name
    + 
    description
    are in context. Decide from those plus the fingerprint — do not pre-read bodies.
  2. On selection: read the body of each chosen 
    skills/<category>/<name>/SKILL.md
    — and only those. Never bulk-load a whole category.
  3. On demand: read a skill's bundled 
    references/
    files only when the subtask needs that depth (the skill body says when).
  4. Re-route on pivot: if the task changes (movement → saving), select and read the newly relevant skill instead of keeping everything loaded.
Announce what you load and why, e.g.: "Detected Godot (
project.godot
). Loading 
godot-2d-movement
for the controller and 
platformer
for jump feel; will open the platformer skill's 
feel-tuning.md
reference if you want coyote-time/buffering."
  1. 预加载内容： 仅将每个技能的
    name
    +
    description
    纳入上下文。结合项目特征信息做出决策——不要预读技能的完整内容。
  2. 选中后阅读： 仅阅读每个选定技能的
    skills/<category>/<name>/SKILL.md
    内容——仅此而已。切勿批量加载整个类别的技能。
  3. 按需阅读： 仅当子任务需要深入信息时，才查看技能附带的
    references/
    目录下的文件（技能内容会说明何时需要）。
  4. 任务转向时重新路由： 若任务发生变化（如从移动系统转向存档系统），选择并阅读新的相关技能，而非保留所有已加载的技能。
需告知用户加载的技能及原因，例如：“检测到Godot引擎（
project.godot
）。为控制器功能加载
godot-2d-movement
技能，为跳跃手感加载
platformer
技能；若需要实现coyote time/输入缓冲，将打开
platformer
技能的
feel-tuning.md
参考文件。”

5. Composition rules

5. 技能组合规则

  • One engine set, additive concepts. Exactly one engine skill set; add the disciplines the task needs and usually at most one genre. Workflows attach independently.
  • Order: engine fundamentals → discipline concept → genre orchestration → workflow.
  • Ownership on overlap: the engine skill owns API/syntax; the discipline skill owns the portable concept/algorithm and defers to the engine skill for code; the genre skill owns structure/glue and links out instead of re-teaching a primitive.
  • Hand-offs: when a genre's 
    composes
    names a slot like 
    *-2d-movement
    , bind it to the detected engine. If that engine lacks the exact skill, see §6 and 
    references/routing-table.md
    ("Binding gaps").
  • 一套引擎技能，叠加概念技能。 仅选择一套引擎技能；添加任务所需的专业领域技能，通常至多添加一种游戏类型技能。工作流技能可独立附加。
  • 顺序： 引擎基础技能 → 专业领域概念技能 → 游戏类型整合技能 → 工作流技能。
  • 重叠内容归属： 引擎技能负责API/语法；专业领域技能负责可移植的概念/算法，代码实现需遵循引擎技能的要求；游戏类型技能负责结构/整合，仅提供链接而非重复教授基础内容。
  • 衔接规则： 当游戏类型技能的
    composes
    字段包含
    *-2d-movement
    这类占位符时，将其绑定到检测到的引擎。若该引擎没有对应的精确技能，请查看第6节及
    references/routing-table.md
    中的“绑定缺口”部分。

6. Unknown-engine & no-skill fallback

6. 未知引擎与无匹配技能的Fallback机制

Engine unknown (no fingerprint, no engine named):
  1. Check the request for a plain-text engine name ("in Unity", "using Phaser"). If found, adopt it.
  2. If the task is a pure concept/genre/workflow question, route straight to the engine-agnostic discipline/genre/workflow skill — no engine needed ("what's a good save format?" → 
    save-systems
    ).
  3. Only if engine choice actually blocks the answer, ask one targeted question ("Which engine — Godot, Unity, Unreal, or a web/other engine?"). If the user has no preference and one is needed, default to Godot (the most fully covered engine here) and say so.
  4. Never invent an engine or load an engine skill on a guess.
Engine known but no skill covers the subtask: load the closest engine skill plus the relevant discipline and state the gap plainly (e.g. "no dedicated Unity 2D-movement skill; using 
unity-csharp-scripting
+ 
unity-physics
"). Never fabricate a skill name.
Conflicting/multiple genres: pick the dominant genre from the phrasing; mention the secondary and offer to load it if the user confirms.
引擎未知（无项目特征、未指定引擎）：
  1. 检查请求中是否有纯文本提及的引擎名称（如“在Unity中”“使用Phaser”）。若有，则采用该引擎。
  2. 若任务是纯概念/游戏类型/工作流问题，直接路由到与引擎无关的专业领域/游戏类型/工作流技能——无需指定引擎（例如“什么是好的存档格式？”→
    save-systems
    ）。
  3. 仅当引擎选择确实会影响答案时，才提出一个针对性问题（“你使用的是哪款引擎——Godot、Unity、Unreal，还是Web/其他引擎？”）。若用户无偏好且必须选择一款引擎，默认选用Godot（此处覆盖最全面的引擎）并告知用户。
  4. 切勿凭空捏造引擎或猜测加载引擎技能。
已知引擎但无匹配子任务的技能： 加载最接近的引擎技能及相关专业领域技能，并明确说明技能缺口（例如“没有专门的Unity 2D移动技能；将使用
unity-csharp-scripting
+
unity-physics
”）。切勿捏造技能名称。
冲突/多种游戏类型： 根据用户表述选择主导游戏类型；提及次要类型，并询问用户是否需要加载该类型的技能。

Worked examples

示例演示

RequestDetected engineSkills loaded (in order)
"add a double jump to my Godot player"Godot (
project.godot
)
godot-2d-movement
→ 
platformer
"make an inventory for my Unity RPG"Unity (
Assets/
+
ProjectSettings/
)
unity-scriptableobjects
→ 
rpg
→ 
save-systems
"procedural dungeon roguelike in Godot"Godot
godot-tilemap
→ 
procedural-gen
→ 
roguelike
"branching dialogue from a 
.yarn
file"		(none required)
dialogue-systems
(+ engine UI skill if an engine is detected)
"how do I design save slots with migration?"(none)
save-systems
only
"publish my game on itch with butler"(any/none)
itch-publish
only
"I want to make a game but don't know what to use"unknown → ask, default Godotrouter asks once; then e.g. 
godot-nodes-scenes
"make hits feel punchy in my Godot game"Godot (
project.godot
)
game-feel
(+ 
camera-systems
for shake)
"the camera should follow my player smoothly"(detected engine)
camera-systems
(+ engine movement skill)
"my Unity game drops to 30 FPS, optimize it"Unity (
Assets/
+
ProjectSettings/
)
performance-optimization
(profile first) → engine skill
请求内容检测到的引擎加载的技能（顺序）
"为我的Godot玩家添加二段跳"Godot（
project.godot
）
godot-2d-movement
→ 
platformer
"为我的Unity RPG制作背包系统"Unity（
Assets/
+
ProjectSettings/
）
unity-scriptableobjects
→ 
rpg
→ 
save-systems
"在Godot中制作程序化地牢肉鸽游戏"Godot
godot-tilemap
→ 
procedural-gen
→ 
roguelike
"从
.yarn
文件实现分支对话"		（无需指定）
dialogue-systems
（若检测到引擎则添加引擎UI技能）
"如何设计带迁移功能的存档槽？"（无需指定）仅加载
save-systems
"用butler工具在itch.io发布我的游戏"（任意/无需指定）仅加载
itch-publish
"我想制作一款游戏但不知道用什么工具"未知 → 询问用户，默认Godot路由工具询问一次；之后例如加载
godot-nodes-scenes
"让我的Godot游戏打击感更强烈"Godot（
project.godot
）
game-feel
（+ 用于震动效果的
camera-systems
）
"让相机平滑跟随我的玩家"（检测到的引擎）
camera-systems
（+ 引擎移动技能）
"我的Unity游戏帧率降到30，需要优化"Unity（
Assets/
+
ProjectSettings/
）
performance-optimization
（先进行性能分析）→ 引擎技能

References

参考资料

  • Full engine fingerprints, secondary signals, and disambiguation: 
    references/engine-detection.md
    .
  • Exhaustive per-skill trigger words, engine bindings, and binding gaps: 
    references/routing-table.md
    .
  • 完整的引擎特征、次要信号及歧义消除规则：
    references/engine-detection.md
    。
  • 详尽的各技能触发词、引擎绑定规则及绑定缺口：
    references/routing-table.md
    。