game-mechanics-design

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Game Mechanics Design

游戏机制设计

Use this skill to make gameplay systems explicit enough for an AI coding agent to implement, test, and tune. The mechanic spec should separate rule structure from presentation so the same idea can be prototyped cheaply before polish.

使用本技能将游戏玩法系统明确化，以便AI编码Agent能够实现、测试和调优。机制规范应将规则结构与表现形式分离，从而可以在打磨前以低成本对同一创意进行原型验证。

Source Traceability

参考来源

Primary source: The Art of Game Design: A Book of Lenses, Third Edition by Jesse Schell, especially chapters 12-14 on mechanics, balance, and puzzles. The workflow is transformed and paraphrased.

Supporting source: MDA, which helps distinguish coded mechanics from the player-visible dynamics and aesthetic experience they produce.

主要来源：Jesse Schell所著《游戏设计艺术：透镜书（第三版）》，尤其是第12-14章关于机制、平衡和谜题的内容。本工作流对其进行了转化和改写。

辅助来源：MDA框架，有助于区分编码实现的机制与其所产生的玩家可感知动态和审美体验。

Workflow

工作流

Identify the core loop: player input, system response, feedback, reward or consequence, and next decision.
Specify mechanics across space, time, objects, attributes, state, actions, rules, goals, skill, chance, and information visibility.
Predict dynamics: dominant strategies, degenerate loops, emergent interactions, pacing, and failure states.
Define player mastery: what starts simple, what becomes expressive, and how players improve.
Produce implementation-ready rules with test cases and tuning parameters.

确定核心循环：玩家输入、系统响应、反馈、奖励或后果，以及下一个决策点。
从空间、时间、对象、属性、状态、动作、规则、目标、技能、随机性、信息可见性等维度定义机制。
预测动态：主导策略、退化循环、涌现交互、节奏和失败状态。
定义玩家精通路径：哪些内容入门简单，哪些会变得富有表现力，以及玩家如何提升。
生成可直接用于实现的规则，附带测试用例和调优参数。

Required Output

所需输出

```
Mechanic Brief
```
: player promise, core loop, and intended dynamics.
```
Rules Model
```
: state, objects, actions, rules, goals, and information.
```
Implementation Notes
```
: data structures, tunable constants, edge cases, and instrumentation.
```
Failure Modes
```
: exploits, dead ends, unreadable outcomes, and boring optimal play.
```
Test Scenarios
```
: deterministic cases the agent can implement.

```
Mechanic Brief
```
：玩家承诺、核心循环和预期动态。
```
Rules Model
```
：状态、对象、动作、规则、目标和信息。
```
Implementation Notes
```
：数据结构、可调常量、边界情况和监测埋点。
```
Failure Modes
```
：漏洞利用、死局、结果不可读和乏味的最优玩法。
```
Test Scenarios
```
：Agent可实现的确定性测试场景。

Local References

本地参考

Before producing a mechanic spec, read:

```
references/core/guide.md
```
```
workflows/mechanic-spec.md
```

在生成机制规范之前，请阅读：

```
references/core/guide.md
```
```
workflows/mechanic-spec.md
```