game-design

Game design principles. GDD structure, balancing, player psychology, progression.

31,392 stars
Complexity: easy

About this skill

This skill equips an AI agent with a comprehensive understanding of core game design concepts, enabling it to assist in various stages of game development. It covers fundamental principles like the iterative '30-second test' for core gameplay loops (ACTION → FEEDBACK → REWARD → REPEAT) with genre-specific examples such as platformers, shooters, puzzles, and RPGs. The skill also delves into crucial aspects like game balancing, understanding player psychology, and structuring effective progression systems. Furthermore, it provides a structured framework for constructing a robust Game Design Document (GDD), detailing essential sections for clear project communication and planning. By internalizing these design tenets, the AI agent can offer structured advice, generate creative design ideas, critically evaluate existing concepts, and help organize comprehensive design documentation.

Best use case

Generating innovative game ideas, structuring a comprehensive Game Design Document, refining existing game mechanics for enhanced player engagement, analyzing and optimizing core gameplay loops, and providing insights into player motivation and progression systems.

Game design principles. GDD structure, balancing, player psychology, progression.

Well-structured and insightful game design advice, a clearer understanding of game mechanics and player engagement, a comprehensive framework for a Game Design Document, and actionable insights for improving game loops and progression systems.

Practical example

Example input

I'm developing a mobile puzzle game. Can you help me define its core loop and outline the essential sections for its Game Design Document?

Example output

Certainly! For a mobile puzzle game, a highly engaging core loop might look like this:

1.  **ACTION:** Player observes the puzzle and plans a move (e.g., sliding blocks, matching colors).
2.  **FEEDBACK:** Player executes a move, game responds with clear visual/audio cues (e.g., blocks animate, satisfying sound, score update).
3.  **REWARD:** Player successfully solves a part of the puzzle, clears a line, earns points, or progresses towards completing the level.
4.  **REPEAT:** Player continues with the next move, driven by the desire to solve the full puzzle and achieve mastery.

Regarding your Game Design Document (GDD), here are essential sections to include for clarity and completeness, ensuring all stakeholders are aligned:

*   **Concept & Vision:** High-level overview, unique selling propositions, target audience, genre, core pillars.
*   **Gameplay Mechanics:** Detailed description of the core loop, controls, game rules, win/loss conditions, difficulty curves.
*   **Game World & Story:** Setting, lore, characters, narrative arcs, progression narrative.
*   **User Interface (UI) & User Experience (UX):** Menus, HUD, player feedback systems, onboarding tutorials, accessibility.
*   **Art & Visuals:** Art style guide, mood board, asset pipeline, character/environment designs, animation principles.
*   **Audio:** Music themes, sound effects, voice acting, audio implementation details.
*   **Technical Details:** Target platforms, game engine, development tools, performance targets, network requirements.
*   **Monetization (if applicable):** Business model, in-app purchases, advertising strategy, virtual economy.
*   **Marketing & Community:** Target market analysis, promotion strategy, community engagement plans, PR.
*   **Development Plan:** Milestones, team roles and responsibilities, production timeline, risk assessment and mitigation.

When to use this skill

  • When initiating a new game project and requiring structured design guidance, refining existing game mechanics for improved player engagement, preparing a comprehensive Game Design Document, or exploring optimal core loop patterns across different game genres.

When not to use this skill

  • For tasks requiring visual design or asset creation, direct coding or implementation of game mechanics, financial modeling or marketing strategy specific to games, real-time game testing or debugging, or soliciting opinions from actual human playtesters.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/game-design/SKILL.md --create-dirs "https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/plugins/antigravity-awesome-skills-claude/skills/game-development/game-design/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/game-design/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How game-design Compares

Feature / Agentgame-designStandard Approach
Platform SupportClaudeLimited / Varies
Context Awareness High Baseline
Installation ComplexityeasyN/A

Frequently Asked Questions

What does this skill do?

Game design principles. GDD structure, balancing, player psychology, progression.

Which AI agents support this skill?

This skill is designed for Claude.

How difficult is it to install?

The installation complexity is rated as easy. You can find the installation instructions above.

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.

Related Guides

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

web-games

31392
from sickn33/antigravity-awesome-skills

Web browser game development principles. Framework selection, WebGPU, optimization, PWA.

Game DevelopmentClaude

pc-games

31392
from sickn33/antigravity-awesome-skills

PC and console game development principles. Engine selection, platform features, optimization strategies.

Game DevelopmentClaude

game-development

31392
from sickn33/antigravity-awesome-skills

Game development orchestrator. Routes to platform-specific skills based on project needs.

Game DevelopmentClaude

vr-ar

31392
from sickn33/antigravity-awesome-skills

VR/AR development principles. Comfort, interaction, performance requirements.

Game DevelopmentClaude

bevy-ecs-expert

31392
from sickn33/antigravity-awesome-skills

Master Bevy's Entity Component System (ECS) in Rust, covering Systems, Queries, Resources, and parallel scheduling.

Game DevelopmentClaude

mobile-design

31392
from sickn33/antigravity-awesome-skills

(Mobile-First · Touch-First · Platform-Respectful)

UI/UX Design & Frontend DevelopmentClaude

kpi-dashboard-design

31392
from sickn33/antigravity-awesome-skills

Comprehensive patterns for designing effective Key Performance Indicator (KPI) dashboards that drive business decisions.

Business Intelligence & AnalyticsClaude

frontend-design

31392
from sickn33/antigravity-awesome-skills

You are a frontend designer-engineer, not a layout generator.

Web DevelopmentClaude

event-store-design

31392
from sickn33/antigravity-awesome-skills

Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.

Software ArchitectureClaude

domain-driven-design

31392
from sickn33/antigravity-awesome-skills

Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.

Software DevelopmentClaude

design-orchestration

31392
from sickn33/antigravity-awesome-skills

Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order.

Workflow AutomationClaude

design-md

31392
from sickn33/antigravity-awesome-skills

Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files

Design SystemsClaude