game-mechanics-design
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.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- game-mechanics-design
- license
- MIT
- metadata
- { "tags": "game-design,mechanics,systems,core-loop,emergence", "version": "0.1.0", "category": "Game Development", "displayName": "Game Mechanics Design" }
- description
- 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.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 2
- 参考文档references/core/guide.md2.5 KB
- 参考文档workflows/mechanic-spec.md758 B
03 SKILL.md 正文
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
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.