game-design
Helps your agent plan and create games. It understands how to make games fun, balanced, and engaging for players.
What it does
This guide helps create more fun and engaging games. It teaches how to think about the player's main actions, how to plan the game's structure, and how to keep players interested.
When to use it
- ✓When thinking about the core actions players will repeat.
- ✓When planning essential parts of a game design document.
- ✓When trying to understand what motivates different player types.
Example of what to ask your AI
“Help me brainstorm the core loop for a racing game.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
It works by explaining concepts like the 'core loop' (action, feedback, reward) and the importance of testing and adjusting the game. It also details important sections of a game design document.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill game-designOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/game-development/game-design/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Game Design Principles
Design thinking for engaging games.
1. Core Loop Design
The 30-Second Test
Prototype a short loop; 30 seconds is a heuristic, not a universal rule:
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 | Actions, feedback and meaningful outcomes |
| 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 | Unpredictable outcomes | Optional rewards with transparent odds |
| 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
Use when designing a playable core loop, preparing a GDD, balancing difficulty, or evaluating progression through playtests.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Verification
Treat tables as design starting points, not guarantees. Prototype the selected mechanic, test accessibility and recovery paths, and measure frame timing, memory and behavior on target hardware before claiming completion. Store submission and licensing requirements must be checked against current official platform documentation.
FAQ
What is a 'core loop'?
It's the sequence of actions a player repeatedly performs in the game, like 'run, jump, collect' in a platformer.
What is a 'GDD'?
It's a Game Design Document, which serves as a detailed plan for the game.
How can I keep players engaged?
By understanding what motivates them (like challenges or discovery), offering interesting rewards, and adjusting the difficulty so the game is neither too easy nor too hard.
Details
Original description by the author
Game design principles. GDD structure, balancing, player psychology, progression.
Popularity
- GitHub stars
- 48k
- Ranking position
- #3073
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
dashboard-builder
Helps your agent create useful monitoring dashboards. It turns data into charts that answer important system questions.
affaan-m/ECC
dev-team
Simulates a collaborative development team where different roles respond to a problem together. It's useful for getting multiple perspectives without manually switching agents.
affaan-m/ECC
ecc-council
Has your agent convene a four-voice council for difficult decisions. It's useful when there are multiple good options and debate is needed before choosing.
affaan-m/ECC