Game Design Framework

Game design

by davila7 · MIT license · ★ 32,299 on GitHub

Game design cover

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

---
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:

Overview

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

Manual install (npx, ZIP)
Claude Codenpx skills add davila7/claude-code-templates --skill game-design -g -a claude-code
Claude Code (degit)npx degit davila7/claude-code-templates/cli-tool/components/skills/creative-design/game-development/game-design#main ~/.claude/skills/game-design
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md2.6 KB
Read SKILL.md here
davila7/main1 file shown
SKILL.md
Show the full text130 lines

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.

1---
2name: game-design
3description: Game design principles. GDD structure, balancing, player psychology, progression.
4allowed-tools: Read, Glob, Grep
5---
6 
7# Game Design Principles
8 
9> Design thinking for engaging games.
10 
11---
12 
13## 1. Core Loop Design
14 
15### The 30-Second Test
16 
17```
18Every game needs a fun 30-second loop:
191. ACTION → Player does something
202. FEEDBACK → Game responds
213. REWARD → Player feels good
224. REPEAT
23```
24 
25### Loop Examples
26 
27| Genre | Core Loop |
28|-------|-----------|
29| Platformer | Run → Jump → Land → Collect |
30| Shooter | Aim → Shoot → Kill → Loot |
31| Puzzle | Observe → Think → Solve → Advance |
32| RPG | Explore → Fight → Level → Gear |
33 
34---
35 
36## 2. Game Design Document (GDD)
37 
38### Essential Sections
39 
40| Section | Content |
41|---------|---------|
42| **Pitch** | One-sentence description |
43| **Core Loop** | 30-second gameplay |
44| **Mechanics** | How systems work |
45| **Progression** | How player advances |
46| **Art Style** | Visual direction |
47| **Audio** | Sound direction |
48 
49### Principles
50 
51- Keep it living (update regularly)
52- Visuals help communicate
53- Less is more (start small)
54 
55---
56 
57## 3. Player Psychology
58 
59### Motivation Types
60 
61| Type | Driven By |
62|------|-----------|
63| **Achiever** | Goals, completion |
64| **Explorer** | Discovery, secrets |
65| **Socializer** | Interaction, community |
66| **Killer** | Competition, dominance |
67 
68### Reward Schedules
69 
70| Schedule | Effect | Use |
71|----------|--------|-----|
72| **Fixed** | Predictable | Milestone rewards |
73| **Variable** | Addictive | Loot drops |
74| **Ratio** | Effort-based | Grind games |
75 
76---
77 
78## 4. Difficulty Balancing
79 
80### Flow State
81 
82```
83Too Hard → Frustration → Quit
84Too Easy → Boredom → Quit
85Just Right → Flow → Engagement
86```
87 
88### Balancing Strategies
89 
90| Strategy | How |
91|----------|-----|
92| **Dynamic** | Adjust to player skill |
93| **Selection** | Let player choose |
94| **Accessibility** | Options for all |
95 
96---
97 
98## 5. Progression Design
99 
100### Progression Types
101 
102| Type | Example |
103|------|---------|
104| **Skill** | Player gets better |
105| **Power** | Character gets stronger |
106| **Content** | New areas unlock |
107| **Story** | Narrative advances |
108 
109### Pacing Principles
110 
111- Early wins (hook quickly)
112- Gradually increase challenge
113- Rest beats between intensity
114- Meaningful choices
115 
116---
117 
118## 6. Anti-Patterns
119 
120| ❌ Don't | ✅ Do |
121|----------|-------|
122| Design in isolation | Playtest constantly |
123| Polish before fun | Prototype first |
124| Force one way to play | Allow player expression |
125| Punish excessively | Reward progress |
126 
127---
128 
129> **Remember:** Fun is discovered through iteration, not designed on paper.
130 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 32,299
Checked
Source
davila7/claude-code-templates ↗
Creator
davila7 · 212 listings
View creator

Similar skills

See all →

More from davila7

Skill2D Game Developmentdavila7/claude-code-templates · by davila72D game development principles. Sprites, tilemaps, physics, camera.★ 32.3k GitHub starsSkill3D Game Development Principlesdavila7/claude-code-templates · by davila73D game development principles. Rendering, shaders, physics, cameras.★ 32.3k GitHub starsSkill3D Web Experience Builderdavila7/claude-code-templates · by davila7Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience.★ 32.3k GitHub starsSkillSplit Test Setupdavila7/claude-code-templates · by davila7When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.★ 32.3k GitHub starsAgentResearch Literature Synthesizerdavila7/claude-code-templates · by davila7Academic research synthesis specialist. Use PROACTIVELY for comprehensive research on academic topics, literature reviews, technical investigations, and well-cited analysis combining multiple sources. <example>Context: A podcast episode needs a segment grounded in peer-reviewed evidence with formal citations. user: "Research the current state of transformer efficiency techniques for the episode, with proper academic citations." assistant: "I'll use the academic-research-synthesizer agent to search arXiv and Semantic Scholar, extract full-text findings via WebFetch, and produce a cited literature synthesis with confidence levels." <commentary>Use academic-research-synthesizer (not comprehensive-researcher) when the episode segment needs peer-reviewed sourcing, formal citation format, and explicit confidence tagging rather than general-purpose multi-source coverage.</commentary></example> <example>Context: The episode-orchestrator has routed a "literature review" request for a technical deep-dive segment. user: "Summarize the research landscape on federated learning privacy guarantees." assistant: "I'll invoke academic-research-synthesizer to systematically search academic sources, note peer-review status per source, and synthesize consensus vs. open debates."</example>★ 32.3k GitHub starsAgentAcademic Research Specialistdavila7/claude-code-templates · by davila7Academic research specialist for scholarly sources, peer-reviewed papers, and academic literature. Use PROACTIVELY for research paper analysis, literature reviews, citation tracking, and academic methodology evaluation. <example>Context: The research-orchestrator has kicked off Phase 4 parallel research on 'efficacy of intermittent fasting' and needs peer-reviewed evidence. user: "Find the academic evidence on intermittent fasting outcomes." assistant: "I'll use the academic-researcher agent to search Semantic Scholar, PubMed, and OpenAlex for peer-reviewed studies and write structured findings to academic-research.md." <commentary>The request is specifically for scholarly/peer-reviewed evidence rather than general web coverage or code, so academic-researcher (not web-researcher or technical-researcher) is the right specialist.</commentary></example> <example>Context: The user wants a literature review comparing methodologies across studies on a topic. user: "Can you review the literature on transformer model interpretability and identify research gaps?" assistant: "Let me invoke the academic-researcher agent to pull foundational and recent papers, extract methodologies, and surface open research gaps." <commentary>Literature review, methodology extraction, and research-gap identification are core academic-researcher capabilities, distinct from technical-researcher's focus on code repositories and implementations.</commentary></example>★ 32.3k GitHub stars