agentleFS
Sign inStart free
xenitV1xenitV1/Antigravity-Workflows/skills/game-development/game-design/SKILL.md

game-design

Skill130 starsChanged 10 months agoMITView on GitHub

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

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep it living (update regularly)

    line 51

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

GenreCore Loop
PlatformerRun → Jump → Land → Collect
ShooterAim → Shoot → Kill → Loot
PuzzleObserve → Think → Solve → Advance
RPGExplore → Fight → Level → Gear

2. Game Design Document (GDD)

Essential Sections

SectionContent
PitchOne-sentence description
Core Loop30-second gameplay
MechanicsHow systems work
ProgressionHow player advances
Art StyleVisual direction
AudioSound direction

Principles

  • Keep it living (update regularly)
  • Visuals help communicate
  • Less is more (start small)

3. Player Psychology

Motivation Types

TypeDriven By
AchieverGoals, completion
ExplorerDiscovery, secrets
SocializerInteraction, community
KillerCompetition, dominance

Reward Schedules

ScheduleEffectUse
FixedPredictableMilestone rewards
VariableAddictiveLoot drops
RatioEffort-basedGrind games

4. Difficulty Balancing

Flow State

Too Hard → Frustration → Quit
Too Easy → Boredom → Quit
Just Right → Flow → Engagement

Balancing Strategies

StrategyHow
DynamicAdjust to player skill
SelectionLet player choose
AccessibilityOptions for all

5. Progression Design

Progression Types

TypeExample
SkillPlayer gets better
PowerCharacter gets stronger
ContentNew areas unlock
StoryNarrative advances

Pacing Principles

  • Early wins (hook quickly)
  • Gradually increase challenge
  • Rest beats between intensity
  • Meaningful choices

6. Anti-Patterns

❌ Don't✅ Do
Design in isolationPlaytest constantly
Polish before funPrototype first
Force one way to playAllow player expression
Punish excessivelyReward progress

Remember: Fun is discovered through iteration, not designed on paper.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free