Our review
Provides structured guidance on game design, covering core loops, game design documents, player psychology, difficulty balancing, progression systems, and common anti-patterns.
Strengths
- Covers a broad range of foundational game design topics
- Offers practical frameworks like the 30-second test and flow state
- Includes tables and examples for quick reference
- Highlights common anti-patterns to avoid
Limitations
- Lacks specific implementation details or technical code examples
- Does not address playtesting methodologies in depth
- May oversimplify complex game psychology topics
Use when you need to structure game concepts, write a GDD, or evaluate the core loop and progression of a game design.
Do not use for technical game development tasks such as programming, 3D modeling, or engine-specific implementation.
Security analysis
SafeThe skill provides conceptual game design guidance and only declares read-only tools (Read, Glob, Grep). It contains no executable commands, destructive instructions, data exfiltration, or unsafe practices.
No concerns found
Examples
I'm designing a puzzle game. Help me define a 30-second core loop and write the first section of a Game Design Document.List the four player types (Bartle taxonomy) and give me reward schedules that would appeal to each.My game has a difficulty spike in level 3. Give me balancing strategies based on flow state.name: game-design description: Game design principles. GDD structure, balancing, player psychology, progression. allowed-tools: Read, Glob, Grep
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.
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.