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. ## When to Use This skill is applicable to execute the workflow or actions described in the overview.
Related Skills
power-bi-report-design-best-practices
Comprehensive Power BI report design and visualization best practices based on Microsoft guidance for creating effective, accessible, and performant reports and dashboards. Triggers on: **/*.{pbix,md,json,txt}
pencil-design
Design UIs in Pencil (.pen files) and generate production code from them. Use when working with .pen files, designing screens or components in Pencil, or generating code from Pencil designs. Triggers on tasks involving Pencil, .pen files, design-to-code workflows, or UI design with the Pencil MCP tools.
mobile-first-design-rules
Focuses on rules and best practices for mobile-first design and responsive typography using tailwind.
minimalist-portfolio-design
Minimalist, typography-focused portfolio design system inspired by neo-brutalist and Swiss design principles. Emphasizes bold typography, generous whitespace, monochromatic color schemes, and elegant simplicity for developer/designer portfolios.
MCP Tool Design
This skill should be used when the user asks to "define a tool", "create tool schema", "design inputSchema", "add tool annotations", "handle file uploads", "tool descriptions", "tool naming", or needs guidance on designing MCP tools for the OpenAI Apps SDK including schemas, annotations, and best practices.
lp-design-spec
Translate a feature requirement into a concrete frontend design specification mapped to the design system, theme tokens, and per-business brand language. Sits between fact-find and plan.
lean-systems-design
Apply Elon Musk-inspired system design thinking for research, engineering, and business workflows: rigorously challenge requirements, delete steps, simplify/optimize what remains, accelerate iteration, then automate. Use when designing or revising systems, processes, or products that need lean, high-velocity execution.
kpi-dashboard-design
Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data ...
frontend-design
Create distinctive, bold UI designs that avoid generic AI aesthetics. This skill should be used when users want frontend components with strong visual identity, creative typography, intentional color palettes, and production-grade animations - specifically to avoid the bland, safe, homogeneous "AI slop" that plagues most generated interfaces.
figma-design
Access Figma designs, extract design systems, and retrieve component specifications. Use when implementing UI from Figma mockups, extracting design tokens, or analyzing design files.
faion-ui-designer
UI design: wireframes, prototypes, design systems, visual design.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.