Game Design Theory

Use theory as a lens that makes a design claim testable. Do not use it as a substitute for player evidence, a universal recipe for fun, or a reason to turn one taxonomy into permanent player labels.

When to use this skill

Use it to:

• trace a mechanic through runtime behavior to a desired player experience;
• explain a weak, confusing, dominant, shallow, or conflicting game system;
• choose between two design variants before full implementation;
• analyze a core loop, progression, reward, resource, uncertainty, or mastery structure;
• frame motivation as a hypothesis about autonomy, competence, or relatedness;
• reconcile playtest observations that support different explanations;
• define the smallest prototype that could disprove a design belief.