unity-mechanics

Unity Mechanics Designer

Design meaningful mechanics that serve your game's core experience — depth over breadth, clarity over complexity

When to Use This Skill

• Proposing a new player ability or interaction system
• Evaluating whether an existing mechanic has enough depth
• Mapping how a mechanic evolves across the game
• Tying a mechanic's design to the game's themes
• Checking a mechanic against the project's constraints

To generate raw mechanic ideas first use unity-brainstorming (standalone skill). For challenge design using these mechanics use unity-puzzle (this plugin). For narrative tie-in use unity-narrative (this plugin).

---

Design Principles

These three principles govern mechanic design regardless of genre:

1. One Mechanic = Many Uses

A mechanic must serve multiple distinct gameplay situations before it earns its place. If it solves only one type of problem, it is not a mechanic — it is a key. Keys bloat the design.

2. Mechanics Evolve, They Don't Multiply

Introduce one mechanic fully before adding another. Complexity comes from combining and deepening existing mechanics, not from adding new ones. Define a mechanic budget for your project and respect it.

3. Every Mechanic Must Teach Something

Each mechanic should communicate a truth about the game world, the character, or the system. The player should be able to say: "Oh — this world works like that."

---

Mechanic Proposal Format

Use this structure for every new mechanic.

## Mechanic: [Name]

**One-line description**: What the player does, in plain language.

**Player input**: Button / gesture / key / mouse action. Define the input complexity.

**Thematic tie**: What does this mechanic say about the world, the character, or the game's themes?

**Gameplay uses** (list 3+):
1. [Primary use case]
2. [Secondary use case]
3. [Tertiary / exploration use]
4. [Optional: combined use with another mechanic]

**Evolution across the game**:
- Early game (Introduce): Simplest version — one correct use, safe environment
- Mid game (Challenge): New constraint applied — pressure, risk, limited resource
- Late game (Combine): Used in combination with other mechanics for compound situations

**Constraints check**:
- [ ] Readable without a UI tooltip
- [ ] Input complexity matches the project's control scheme
- [ ] Fails gracefully — wrong use produces a clear, readable result
- [ ] Does not require another mechanic to be learned first
- [ ] Fits within the project's mechanic budget