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.
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.
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.
Local References
Before producing a mechanic spec, read:
references/core/guide.mdworkflows/mechanic-spec.md
1---2name: game-mechanics-design3description: Design, inspect, or repair game mechanics, core loops, rules, goals, actions, state, chance, secrets, skills, and emergent dynamics. Use when building gameplay systems, combat, puzzles, progression, simulations, board/card mechanics, or any feature where rules create player behavior.4license: MIT5---67# Game Mechanics Design89Use 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.1011## Source Traceability1213Primary 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.1415Supporting source: MDA, which helps distinguish coded mechanics from the player-visible dynamics and aesthetic experience they produce.1617## Workflow18191. Identify the core loop: player input, system response, feedback, reward or consequence, and next decision.202. Specify mechanics across space, time, objects, attributes, state, actions, rules, goals, skill, chance, and information visibility.213. Predict dynamics: dominant strategies, degenerate loops, emergent interactions, pacing, and failure states.224. Define player mastery: what starts simple, what becomes expressive, and how players improve.235. Produce implementation-ready rules with test cases and tuning parameters.2425## Required Output2627- `Mechanic Brief`: player promise, core loop, and intended dynamics.28- `Rules Model`: state, objects, actions, rules, goals, and information.29- `Implementation Notes`: data structures, tunable constants, edge cases, and instrumentation.30- `Failure Modes`: exploits, dead ends, unreadable outcomes, and boring optimal play.31- `Test Scenarios`: deterministic cases the agent can implement.3233## Local References3435Before producing a mechanic spec, read:3637- `references/core/guide.md`38- `workflows/mechanic-spec.md`
ConcertoNotes