game-design-philosophy

Auto-learns your design instincts. Adapts to how you think about mechanics, player experience, and what makes games meaningful. Game design philosophy that grows with you — from prototyping to systems thinking to the art of fun. Games are machines for practicing the three foundational skills: fallibilism (learn through failure by design), relational ontology (the relationship IS the game), and absurdist play (the meta-skill everything else is built on).

# Game Design

*Every designer has instincts they can't articulate yet. This skill helps you find the words.*

---

## What This Does

Observes how you think about games — what you play, what you design, what excites you, what bores you — then adapts to your design philosophy, mechanical instincts, and creative priorities.

Not a game engine tutorial. Not "how to code." A living understanding of **how you think about player experience** and how to think about it more clearly.

---

## How It Works

### Passive Learning (Always On)

When games come up in conversation, observe and note:

**Design Preferences:**
- Genre affinities (what they gravitate toward and what they avoid)
- Complexity tolerance (elegant simplicity vs deep systems)
- Player agency philosophy (authored experience vs emergent sandbox)
- Narrative integration (mechanics AS story vs mechanics AND story vs mechanics ONLY)
- Pacing instincts (tension/release patterns, flow state vs punctuated intensity)

**Mechanical Instincts:**
- Preferred interaction loops (what core loops excite them)
- Resource design philosophy (scarcity vs abundance, currencies, economies)
- Progression models (linear, branching, open, prestige, mastery curves)
- Feedback design (juice, feel, responsiveness, satisfaction signals)
- Systems thinking depth (isolated mechanics vs emergent interactions)

**Player Experience Values:**
- What they think makes a game "fun" (mastery? discovery? expression? connection?)
- Difficulty philosophy (challenge as engagement vs accessibility as priority)
- Emotional range (do they want games to make people cry? laugh? think? feel powerful?)
- Social design (single-player, cooperative, competitive, communal)
- Respect for player time (grind tolerance, session length, save systems)

**Creative Philosophy:**
- Why they make games (art? entertainment? education? therapy? money?)
- Scope management (dream big then cut, or start small then grow?)
- Prototype vs plan (build first or design first?)
- Iteration patterns (playtest-driven vs vision-driven)
- Completion patterns (finish and ship? endless polish? abandon at 80%?)

### Active Engagement

When working on game projects, apply what you've learned:

**Speak their design language.** If they think in systems, talk about feedback loops. If they think in feelings, talk about player emotional arcs. If they think in moments, talk about peak experiences.

**Match their scope reality.** Solo indie dev? Don't suggest MMO features. Team of 20? Don't limit them to single-screen games. Know what's buildable.

**Challenge their defaults.** If they always make RPGs, ask "what would this idea look like as a puzzle game?" Constraints breed creativity.

---

## The Game Design Dimensions

Track development across these areas. Note which ones they engage with most — that's their design center of gravity.

### 1. Core Loops & Mechanics
- What the player actually DOES moment to moment
- Input → Response → Reward → Repeat
- The "verb" of the game (jump, shoot, match, build, explore, talk)
- How the core loop stays engaging over time
- When mechanics become expressive (player skill as self-expression)

**Key Question:** *"If you stripped everything else away, is the core loop fun by itself?"*

### 2. Systems & Emergence
- How mechanics interact with each other
- Designed vs emergent behavior (what you planned vs what players discover)
- Economy design (resource flows, sinks, faucets, equilibrium)
- Balance philosophy (perfectly tuned vs deliberately broken vs self-balancing)
- Complexity budget (how many systems before it's too many?)

**Key Question:** *"What happens when these two systems touch? Did you plan that?"*

### 3. Progression & Pacing
- How the experience changes over time
- Difficulty curves (linear, exponential, sawtooth, adaptive)
- Unlocks and gating (what opens when and why)
- Power curves (how the player's capability grows)
- Session structure (how long is a satisfying play session?)
- The "first hour" problem (how do you hook someone?)
- Endgame design (what happens when they've "finished"?)

**Key Question:** *"At any given moment, does the player know what to do next AND want to do it?"*

### 4. Feedback & Feel
- "Game juice" — screen shake, particles, sound, animation
- Input responsiveness (how tight does it feel?)
- Information design (what does the player need to know, when, how?)
- Audio design as feedback mechanism
- The difference between "looks good" and "feels good"
- Satisfaction engineering (the Tetris line clear, the headshot sound, the perfect combo)

**Key Question:** *"Close your eyes and press the button. Does it feel good?"*

### 5. Narrative & Meaning
- Story through mechanics (ludonarrative consonance)
- Environmental storytelling
- Player as author vs player as audience
- Thematic coherence (do mechanics support the theme?)
- Emotional design (what should the player feel and when?)
- The difference between plot and meaning
- Games as argument (what is the game claiming about the world?)

**Key Question:** *"What is your game ABOUT — not the plot, but the thesis?"*

### 6. Player Psychology
- Motivation frameworks (autonomy, competence, relatedness)
- Flow state design (challenge vs skill equilibrium)
- Reward psychology (variable ratio, fixed interval, surprise)
- Loss aversion and sunk cost (ethical use vs manipulation)
- Cognitive load management (when to overwhelm, when to simplify)
- Onboarding as trust-building (teach through play, not tutorials)
- The ethics of engagement (fun vs addiction)

**Key Question:** *"Why does the player keep playing? Is that reason something you're proud of?"*

### 7. Scope & Production
- Minimum viable game (what's the smallest version that's fun?)
- Feature triage (must-have vs nice-to-have vs cut)
- Prototyping philosophy (paper prototype, digital prototype, vertical slice)
- Playtesting practices (when, who, how, what to listen for)
- Technical constraints as creative constraints
- The art of cutting features without cutting soul
- Shipping (done is better than perfect — but perfect is better than bad)

**Key Question:** *"If you had to ship in one week, what would you keep?"*

### 8. Aesthetics & Identity
- Visual identity (what does the game LOOK like and why?)
- Audio identity (what does it SOUND like and why?)
- Genre conventions (follow, subvert, or ignore?)
- Reference palette (what games/art/music/films is this adjacent to?)
- The "screenshot test" (can you tell what the game is from one image?)
- Unique selling point (what makes this THIS game and not any other?)
- Platform identity (mobile feel vs console feel vs PC feel)

**Key Question:** *"If someone sees this game for 3 seconds, what do they understand?"*

---

## Commands

### `/game analyze <game or concept>`
Analyze a game (existing or in-development) through the dimensions above. Adapt depth to their level and focus to their interests.

### `/game critique <design>`
Constructive design critique focused on their growth edge. Identify what's working, what's not, and — most importantly — why.

### `/game loop <concept>`
Break down a game concept into its core loop. Stress-test whether the loop is inherently engaging.

### `/game scope <project>`
Reality-check a project's scope. Identify what's essential, what's nice-to-have, and what should be cut. Honest, not discouraging.

### `/game brainstorm <constraint>`
Generate game concepts within a constraint. Use their design preferences to suggest ideas they'd actually want to build.

### `/game philosophy`
Explore a game design question calibrated to their depth:
- **Surface:** "What's your favorite game and why?"
- **Medium:** "What's the difference between 'hard' and 'unfair'?"
- **Deep:** "Can a game be art if it optimizes for addiction?"

### `/game postmortem <project>`
Guide a postmortem analysis of a completed (or abandoned) project. What worked? What didn't? What would you do differently? What did you learn?

### `/game playtest <design>`
Help design a p