Game Design

Design principles for tactics and strategy games. Use when designing new mechanics, tuning existing systems, adding units or abilities, adjusting difficulty, or making any game design decision. Triggers on discussions about game balance, unit roles, terrain, pacing, spawning, healing, combat, win/loss conditions, or UI for conveying game state.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add roby2358/skills --skill game-design
Manual install
git clone --depth 1 https://github.com/roby2358/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/game-design ~/.claude/skills/game-design

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Game Design Principles

## Workflow

When designing a new game or a major new system, start by creating a **DYNAMICS.md** document. This is not a spec — it's a design journal that answers "Why is this fun?" before any mechanics are written.

### DYNAMICS.md Process

1. **Theme first.** What is the emotional experience? Not setting or plot — the *feeling*. "Desperate last stand against encroaching doom" is a theme. "Fantasy tactics on a hex grid" is not.
2. **Choose 2-3 key drivers** from the list below that the theme naturally activates. These are the load-bearing pillars. Every other mechanic weaves into them.
3. **Design key mechanics** — one per driver. Each mechanic should be a single sentence. If it takes a paragraph to explain, it's too complex or it's actually two mechanics.
4. **Weave secondary mechanics** into the key ones. Every new mechanic must connect to an existing one. If it stands alone, it's bloat. Ask: "What existing mechanic does this make more interesting?"
5. **Gut check every mechanic.** Does it satisfy common sense? If a player encounters it cold, will it feel intuitive or backwards? A mechanic that requires explanation is fighting the player's instincts. Fire should hurt, armor should protect, retreating to safety should heal. When a mechanic *must* defy intuition (e.g., closing a spawn point makes remaining enemies stronger), the player needs to feel the logic immediately — otherwise it reads as a bug, not a design.
Read the full skill on GitHub

Details

Skill name
game-design
Path
game-design/SKILL.md
Repo updated
14 November 2026

FAQ

What does the Game Design skill do?

Design principles for tactics and strategy games. Use when designing new mechanics, tuning existing systems, adding units or abilities, adjusting difficulty, or making any game design decision. Triggers on discussions about game balance, unit roles, terrain, pacing, spawning, healing, combat, win/loss conditions, or UI for conveying game state.

How do I install the Game Design skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add roby2358/skills --skill game-design. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Game Design popular?

It lives in roby2358/skills, which has 5 GitHub stars and 0 forks.

Related skills

Coding

5

roby2358/skills

Project-specific coding conventions and constraints. Use when writing, modifying, or refactoring any code, implementing features, writing tests, or building MCP servers in this project.

Software Development

Game Productize

5

roby2358/skills

Audit a browser game for ship-readiness and produce a tiered gap list: a SHIP.md in the game repo plus pjpd tasks. Finds what gets forgotten between "the game works" and "a stranger can play it": title/menus/end screens, save and resume, audio and settings, onboarding, the mobile "sorry" screen, localization readiness, error recovery, hosting on the author's site and on portals (itch.io, Newgrounds), credits, asset licenses, and AI disclosure. Use when the user says "productize", "/game-productize", "get this game ready to ship/release/publish/launch", "what's missing before I launch", "prep f

Documents & Office Files

Horizon

5

roby2358/skills

Structured pause before building. Use when about to implement a feature, ship a change, or when the user invokes /horizon. Forces examination of what's beyond the immediate solution — whether this should be built at all, whether the design is right, whether existing code needs attention first. Triggers on feature requests, implementation starts, or when the user wants to challenge the impulse to build.

Software Development

Implement

5

roby2358/skills

Implement an app from its design docs, either a SPEC.md or the ONTOLOGY.md + CRITERIA.md set (with DYNAMICS and RATIONALE), in order (contract, then headless core and tests, then tuning, then UI), then review JS and CSS and reconcile the docs. Use after creating or updating a SPEC.md or ONTOLOGY.md.

Frontend & Design

Frontend Review

9

sandbaseai/workbuddy-skill

Use when reviewing frontend changes for interaction correctness, responsive behavior, accessibility, performance, state handling, and browser-facing regressions.

Frontend & Design

Integration Health Check

9

sandbaseai/workbuddy-skill

Use first when an integration context is ambiguous or a user needs to verify connection, credentials, accessible organizations, projects, or capabilities before taking an action.

Frontend & Design

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.