Game Design Theory
Structure a game’s core loop, rewards, difficulty, and GDD pillars using MDA and player-motivation frameworks before heavy implementation.
Overview
Game Design Theory is an agent skill most often used in Validate (also Idea, Build) that applies MDA and related frameworks to core loops, rewards, and GDD pillars.
Install
npx skills add https://github.com/pluginagentmarketplace/custom-plugin-game-developer --skill game-design-theoryWhat is this skill?
- MDA framework: mechanics, dynamics, aesthetics mapped to player experience
- Core loop, reward systems, difficulty curves, and player engagement elements
- Optional lenses: Bartle, flow, reward_systems with game-type enums
- Bonded game-designer workflow with retry policy and design quality observability hooks
- Outputs align to GDD and design_pillars documentation artifacts
- MDA framework with mechanics, dynamics, and aesthetics layers
- Core element set: core_loop, reward_systems, difficulty_curves, player_engagement
- Optional framework enum: mda, bartle, flow, reward_systems
Adoption & trust: 1.4k installs on skills.sh; 30 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a game idea but no clear model linking rules, player behavior, and fun—so scope creeps and balance debates stay subjective.
Who is it for?
Solo devs designing indie games who want MDA- and motivation-grounded GDD sections before committing to a vertical slice.
Skip if: Teams that only need engine tutorials, shader work, or live-ops analytics with an already locked design bible.
When should I use this skill?
Scoping or iterating game design, writing GDD sections, or analyzing balance and player motivation before or during development.
What do I get? / Deliverables
You get structured design pillars, documented core loop and progression choices, and framework-backed rationale to hand off to prototyping or implementation.
- GDD-oriented notes on core loop, rewards, progression, and design pillars
- Framework-backed analysis (MDA and optional Bartle, flow, or reward systems)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Design theory and GDD elements belong on the shelf where you scope mechanics and pillars before committing to a full build. The skill outputs design pillars, GDD-oriented elements, and balance framing—not engine code or asset pipelines.
Where it fits
Compare two casual puzzle concepts using MDA aesthetics before picking which prototype to fund.
Draft design pillars and a core loop section for a vertical-slice GDD ahead of playtesting.
Align reward pacing and difficulty curve targets with flow framework notes for a first playable.
Revisit reward_systems parameter choices when milestone playtests show engagement dropping mid-campaign.
How it compares
Design methodology and GDD framing skill, not a Unity/Unreal implementation or asset pipeline integration.
Common Questions / FAQ
Who is game-design-theory for?
Indie and solo game developers who act as designer and programmer and need systematic theory for loops, rewards, and difficulty before production.
When should I use game-design-theory?
Use it in Idea/research to compare concepts, Validate/scope to write GDD pillars and core loops, and Build/pm when rebalancing progression against original aesthetics goals.
Is game-design-theory safe to install?
It focuses on design analysis and documentation; review the Security Audits panel on this Prism page and any bonded agent scripts before enabling automated runs.
SKILL.md
READMESKILL.md - Game Design Theory
elements: - core_loop - reward_systems - difficulty_curves - player_engagement documentation: - gdd - design_pillars # Game Design Theory ## Core Elements - Core loop - Reward systems - Difficulty curves - Player motivation #!/usr/bin/env python3 import json def analyze(): return {"elements": ["core_loop", "rewards", "progression"], "docs": ["gdd", "pillars"]} if __name__ == "__main__": print(json.dumps(analyze(), indent=2)) --- name: game-design-theory version: "2.0.0" description: | Comprehensive game design theory covering MDA framework, player psychology, balance principles, and progression systems. Master why games are fun. sasmp_version: "1.3.0" bonded_agent: 01-game-designer bond_type: PRIMARY_BOND parameters: - name: framework type: string required: false validation: enum: [mda, bartle, flow, reward_systems] - name: game_type type: string required: false validation: enum: [action, rpg, puzzle, strategy, casual, simulation] retry_policy: enabled: true max_attempts: 3 backoff: exponential observability: log_events: [start, complete, error] metrics: [design_quality_score, iteration_count] --- # Game Design Theory ## The MDA Framework ``` ┌─────────────────────────────────────────────────────────────┐ │ MDA FRAMEWORK │ ├─────────────────────────────────────────────────────────────┤ │ MECHANICS (Rules): │ │ → Player actions, constraints, state changes │ │ → Example: Jump has height limit, costs stamina │ │ ↓ │ │ DYNAMICS (Behavior): │ │ → Emergent gameplay from mechanic interactions │ │ → Example: Wall-jump combos, speedrun routes │ │ ↓ │ │ AESTHETICS (Experience): │ │ → Emotional responses: Fun, tension, achievement │ │ → Example: Flow state, satisfaction, immersion │ └─────────────────────────────────────────────────────────────┘ ``` ## Core Game Loop ``` ┌─────────────────────────────────────────────────────────────┐ │ ENGAGEMENT LOOP │ ├─────────────────────────────────────────────────────────────┤ │ 1. INPUT → Player takes action │ │ 2. PROCESS → Game calculates results │ │ 3. FEEDBACK → Immediate visual/audio response │ │ 4. REWARD → Progress, points, unlocks │ │ 5. REPEAT → Loop invites next iteration │ │ │ │ Loop Quality Criteria: │ │ ✓ Fast feedback (< 100ms) │ │ ✓ Clear causation │ │ ✓ Rewarding outcomes │ │ ✓ Compelling repetition │ └─────────────────────────────────────────────────────────────┘ ``` ## Flow Channel (Csikszentmihalyi) ``` Anxiety ↑ Hard │ ████ │ ██████ ← FLOW CHANNEL Skill │ ████████ (Optimal Engagement) Level │████████████ Easy │██████████████ └──────────────────→ Low Challenge High TARGET: Match challenge to player skill ``` ## Player Psychology ### Bartle's Player Types | Type | Motivation | Design For | |------|------------|------------| | Achiever | Goals, progression | Achievements, levels | | Explorer | Discovery, secrets | Hidden content, lore | | Socializer | Community | Chat, guilds, co-op | | Killer | Competition | PvP, leaderboards | ### Motivation Drivers ``` SELF-DETERMINATION THEORY: ┌─────────────────────────────────────────────────────────────┐ │ AUTONOMY: Choice and