Game Backend Selector
Goal
Select the backend profile that best serves the requested outcome.
Use
./shared/reference/backend-profiles.md.
Deliverable
Write
docs/game-studio/backend-decision.md.
Rules
- - Prefer capabilities over brand or fandom.
- If the project already has a workable backend, bias toward it unless it is the blocker.
- Optimize for the chosen quality target, not just the fastest toy result.
- Respect project state: live iteration and greenfield do not deserve the same backend decision policy.
Compare mode
Use compare mode only when:
- - the backend choice is genuinely uncertain,
- or the user explicitly requests comparison.
When compare mode is used:
- - warn that it will usually cost more tokens and time,
- keep the comparison narrow,
- define the winner criteria before exploring.
Specialist follow-through
After choosing a backend profile, route to a concrete specialist when needed:
- -
game-web-2d-specialist for web-2d-ui-first or INLINECODE4 - INLINECODE5 for INLINECODE6
Top-level planning remains stack-neutral.
Implementation guidance should still become concrete once a backend family is chosen.
游戏后端选择器
目标
选择最能满足请求结果的后端配置文件。
参考 ./shared/reference/backend-profiles.md。
交付物
编写 docs/game-studio/backend-decision.md。
规则
- - 优先考虑能力而非品牌或粉丝偏好。
- 如果项目已有可用的后端，除非该后端成为阻碍，否则倾向于继续使用。
- 针对所选的质量目标进行优化，而非仅仅追求最快的演示效果。
- 尊重项目状态：持续迭代中的项目与全新项目不应采用相同的后端决策策略。
对比模式
仅在以下情况下使用对比模式：
- - 后端选择确实存在不确定性，
- 或用户明确要求进行比较。
使用对比模式时：
- - 需警告通常会消耗更多令牌和时间，
- 保持对比范围狭窄，
- 在探索前先定义胜出标准。
专家跟进
选择后端配置文件后，在需要时转接至具体专家：
- - game-web-2d-specialist 用于 web-2d-ui-first 或 web-2d-world-first
- game-web-3d-specialist 用于 web-3d-preview
顶层规划保持技术栈中立。
一旦选定后端系列，实施指导应变得具体化。
