game-design
Game design principles. GDD structure, balancing, player psychology, progression.
Best use case
game-design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Game design principles. GDD structure, balancing, player psychology, progression.
Teams using game-design should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/game-design/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How game-design Compares
| Feature / Agent | game-design | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Game design principles. GDD structure, balancing, player psychology, progression.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Game Design Principles > Design thinking for engaging games. --- ## 1. Core Loop Design ### The 30-Second Test ``` Every game needs a fun 30-second loop: 1. ACTION → Player does something 2. FEEDBACK → Game responds 3. REWARD → Player feels good 4. REPEAT ``` ### Loop Examples | Genre | Core Loop | |-------|-----------| | Platformer | Run → Jump → Land → Collect | | Shooter | Aim → Shoot → Kill → Loot | | Puzzle | Observe → Think → Solve → Advance | | RPG | Explore → Fight → Level → Gear | --- ## 2. Game Design Document (GDD) ### Essential Sections | Section | Content | |---------|---------| | **Pitch** | One-sentence description | | **Core Loop** | 30-second gameplay | | **Mechanics** | How systems work | | **Progression** | How player advances | | **Art Style** | Visual direction | | **Audio** | Sound direction | ### Principles - Keep it living (update regularly) - Visuals help communicate - Less is more (start small) --- ## 3. Player Psychology ### Motivation Types | Type | Driven By | |------|-----------| | **Achiever** | Goals, completion | | **Explorer** | Discovery, secrets | | **Socializer** | Interaction, community | | **Killer** | Competition, dominance | ### Reward Schedules | Schedule | Effect | Use | |----------|--------|-----| | **Fixed** | Predictable | Milestone rewards | | **Variable** | Addictive | Loot drops | | **Ratio** | Effort-based | Grind games | --- ## 4. Difficulty Balancing ### Flow State ``` Too Hard → Frustration → Quit Too Easy → Boredom → Quit Just Right → Flow → Engagement ``` ### Balancing Strategies | Strategy | How | |----------|-----| | **Dynamic** | Adjust to player skill | | **Selection** | Let player choose | | **Accessibility** | Options for all | --- ## 5. Progression Design ### Progression Types | Type | Example | |------|---------| | **Skill** | Player gets better | | **Power** | Character gets stronger | | **Content** | New areas unlock | | **Story** | Narrative advances | ### Pacing Principles - Early wins (hook quickly) - Gradually increase challenge - Rest beats between intensity - Meaningful choices --- ## 6. Anti-Patterns | ❌ Don't | ✅ Do | |----------|-------| | Design in isolation | Playtest constantly | | Polish before fun | Prototype first | | Force one way to play | Allow player expression | | Punish excessively | Reward progress | --- > **Remember:** Fun is discovered through iteration, not designed on paper.
Related Skills
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
mobile-design
Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.
web-games
Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
game-development
Game development orchestrator. Routes to platform-specific skills based on project needs.
pc-games
PC and console game development principles. Engine selection, platform features, optimization strategies.
mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.
game-audio
Game audio principles. Sound design, music integration, adaptive audio systems.
game-art
Game art principles. Visual style selection, asset pipeline, animation workflow.
3d-games
3D game development principles. Rendering, shaders, physics, cameras.
2d-games
2D game development principles. Sprites, tilemaps, physics, camera.
frontend-design
Design thinking and decision-making for web UI. Use when designing components, layouts, color schemes, typography, or creating aesthetic interfaces. Teaches principles, not fixed values.
database-design
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.