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
vpc-network-designer
Vpc Network Designer - Auto-activating skill for AWS Skills. Triggers on: vpc network designer, vpc network designer Part of the AWS Skills skill category.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "premium website", "portfolio site", "scroll animations", "Awwwards quality", or "brand experience". Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography. Trigger with 'top', 'design'.
rest-endpoint-designer
Rest Endpoint Designer - Auto-activating skill for API Development. Triggers on: rest endpoint designer, rest endpoint designer Part of the API Development skill category.
ios-hig-design
Build native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", or "HIG compliance". Covers navigation patterns, accessibility, SF Symbols, and platform conventions. For general UI polish, see refactoring-ui. For affordance design, see design-everyday-things. Trigger with 'ios', 'hig', 'design'.
dynamodb-table-designer
Dynamodb Table Designer - Auto-activating skill for AWS Skills. Triggers on: dynamodb table designer, dynamodb table designer Part of the AWS Skills skill category.
designing-database-schemas
Process use when you need to work with database schema design. This skill provides schema design and migrations with comprehensive guidance and automation. Trigger with phrases like "design schema", "create migration", or "model database".
design-sprint
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", or "de-risk before building". Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done. Trigger with 'design', 'sprint'.
design-everyday-things
Analyze and apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", or "fault tolerance". Covers the gulfs of execution and evaluation. For usability scoring, see ux-heuristics. For iOS-specific patterns, see ios-hig-design. Trigger with 'design', 'everyday', 'things'.
create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.
web-design-reviewer
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.
power-bi-report-design-consultation
Power BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design.
power-bi-model-design-review
Comprehensive Power BI data model design review prompt for evaluating model architecture, relationships, and optimization opportunities.