A quick index of the game design skills currently available in the workspace.
Define the emotional core, atmosphere, and vibe of a game, feature, event, or theme. Best for emotional identity, moodboards, and tone alignment.
Turn an emotional canvas into a curated visual moodboard with candidate gathering, hard rejection, palette references, clean or annotated board modes, and JPG/HTML output. Best for turning tone direction into actual visual reference boards instead of leaving it as prose.
Turn a rough game idea into a practical order of work for a solo dev, duo, or small team. Best for beginner-friendly scoping, first-milestone planning, and deciding what to build first versus postpone.
Figure out which roles, skills, or disciplines are missing or weakly covered for a game concept and target milestone. Also works in minimum-team mode when no current team is described.
Estimate likely budget ranges for a game concept based on scope, milestone, current team, work model, and geography. Also works in scenario mode when the team is unknown.
Estimate likely development time ranges for a game concept based on scope, milestone, current team, availability, and production constraints. Also works in scenario mode when the team is unknown and in target-date mode when the user wants a realism check on a deadline.
Use the GROW model to structure feature discussions through Goal, Reality, Options, and Will. Good for teams that need more process and clearer decisions.
Audit what kinds of motivation a design creates: reward-driven, status-driven, value-endorsed, identity-based, or intrinsic.
Audit whether a design satisfies or denies autonomy, competence, and relatedness. Good for spotting emotionally nourishing versus quietly depleting systems.
Audit a feature or system through the lens of Achievers, Explorers, Socializers, and Killers to understand which player archetypes it serves, neglects, or harms.
Audit a game, feature, or system through a more granular player motivation taxonomy to understand which detailed motivation segments it serves, neglects, or quietly repels. Best for cases where Bartle is too coarse and you need distinctions like competitive status versus strategic leadership, creative authorship versus narrative immersion, or belonging versus reward-chasing.
Audit a game, feature, or system through the Big Five / OCEAN personality traits to understand what kinds of players feel comfortable with its novelty, structure, social intensity, conflict style, and emotional pressure. Best for exposing hidden personality-fit assumptions and diagnosing whether a design is too ambiguous, maintenance-heavy, socially loud, adversarial, or stressful for parts of the audience.
Audit a game, feature, live-ops layer, social system, or multiplayer concept for the quality and fit of its social design. Best for evaluating collaboration, competition, collaborate-to-compete structures, synchronous versus asynchronous play, community formation, and vanity/status systems.
Map uncertainty, identify hidden unknowns, and decide what should be prototyped before production commitment.
Turn a vague idea into a clear feature goal with purpose, fit, success criteria, and constraints.
Generate multiple credible solution paths before committing to one.
Force explicit comparison across at least five candidate approaches.
Get unstuck by isolating the main blocker, imagining it removed, and deriving workaround paths.
Start from the ideal player-facing result and work backward to the design steps needed to reach it.
Solve new problems by adapting, extending, recombining, or retuning what already exists.
Compare candidate options by impact, cost, risk, fit, and timing to decide what to do now versus later.
Audit a feature, flow, onboarding step, retention mechanic, or monetization prompt using Motivation, Ability, and Prompt. Best for diagnosing weak feature adoption, friction, and mistimed prompts.
Audit a game feature, combat system, loot table, reward loop, procedural system, or chance mechanic by how players are likely to perceive its randomness. Best for spotting streak pain, gambler's-fallacy-style expectation errors, rigged-feeling outcomes, and cases where randomness undermines competence or agency.
Audit how players explain success and failure through locus, stability, and controllability. Best for spotting when players blame the system, luck, or hidden rules instead of seeing failure as learnable.
Audit whether challenge and player skill stay aligned over time. Best for identifying boredom plateaus, anxiety spikes, and exact moments where pacing or difficulty breaks engagement.
Audit perceived fairness and retry-worthiness by combining attribution, flow, and randomness-perception lenses. Best for diagnosing why a design feels hostile, suspicious, or anger-inducing even when it is technically functional.
Audit what happens after failure: what players lose, what they learn, how fast they retry, and whether the loop creates momentum or resignation.
Design original tabletop or digital RPG systems, character classes, and focused subsystems. It can work from an original brief or selectively adapt documented SRD 5.1 or 5.2.1 mechanical patterns, while keeping provenance, attribution, and excluded D&D identity material separate. Best for core rules engines, combat, magic, progression, class design, and design-ready system documentation.
Extract the core player fantasy from a game, feature, or pitch based on what the design actually lets the player do, feel, and become. Best for testing whether the claimed fantasy is real, generic, conflicted, or unsupported.
Extract the ideal player persona and anti-persona from the design itself. Best for behavior-first audience definition, with optional demographic, market-validation, comparable-title, and pitch-facing audience-summary layers when explicitly requested.
Extract 3 to 5 actionable design pillars from what the game actually rewards and prioritizes. Best for replacing vague slogans with testable, tradeoff-driven principles.
Extract the actual core loop from repeated player action, feedback, reward, and renewed intent. Best for exposing feature soup, dead steps, false loops, or weak motivational closure.
Stress-test a concept through a deliberately provocative, ambition-seeking lens. Best for calling out safe, emotionally weak ideas and pushing them toward sharper fantasy, reactivity, and memorable moments before grounding them again.
Audit a game, feature, or proposal through the lens of fast versus slow thinking. Best for identifying whether a design asks for instinctive versus analytical cognition, where those demands mismatch the fantasy or pacing, and where handoffs between reactive and reflective play become exhausting or fake-deep.
Audit a game, feature, session, level, event, onboarding flow, reward sequence, or return-player experience through the lens of the peak-end rule. Best for identifying which moments dominate memory, whether the emotional high points are strong enough, and whether the ending leaves the right aftertaste.
Audit a game, feature, task system, quest flow, event track, puzzle chain, progression layer, or return loop through the lens of the Zeigarnik effect. Best for evaluating whether unfinished business creates healthy return pull, curiosity, and momentum, or whether it turns into guilt, clutter, and manipulative pressure.
Audit FTUE and onboarding flows through the Hero's Journey lens: call to adventure, mentor, threshold crossing, early autonomy, and first-session emotional connection.
Audit a game or feature for goal density, immediacy of goals, short/mid/long-term goal breakdown, safe stopping points, and return triggers.
Audit a game, feature flow, economy path, onboarding journey, progression chain, or live-ops loop for friction quality and friction accumulation. Best for diagnosing where productive challenge becomes harmful obstruction, where multiple constraints stack badly, and where players slow, stall, or churn.
Infer a player's underlying values and motivational priorities from behavior, then translate those into design implications. Best for behavior-first personalization, segmentation, event/offer targeting, and diagnosing where the design is asking for values the player does not strongly hold.
Reframe a player's current situation to reveal new meaning, goals, roles, or playstyles without changing the underlying mechanics. Best for stagnation recovery, adaptive guidance, alternate challenge framing, and judging when an interpretive intervention is useful versus when the real issue is structural.
Evaluate a game's social features and multiplayer elements by their potential to create social satisfaction versus social dissatisfaction. Best for classifying social systems as basic, critical, booster, or secondary, and for identifying which features are missing foundations, carrying too much risk, or offering easy social upside.
Design or audit prosocial experiences in session-based multiplayer games using a three-phase model built around Setup, Little Loops, and Long Tail. Best for co-op, team-based, and repeat-session multiplayer formats where prosociality needs to be primed before play, repeated during play, and preserved after play.
Audit a game pitch deck for structure, clarity, dream-versus-proof balance, business-case strength, readability, and publisher-fit.
Create a concise one-page game design document and export it as both markdown and PDF. Best for turning rough game notes into a compact, readable concept sheet that captures identity, pillars, features, interface, art/audio direction, audience, and milestone framing.
Use oblique prompts, sideways reframing, and playful provocations to break creative block and generate weird-but-useful next directions.
Perform a hostile-but-constructive pre-mortem on a feature, system, pitch, or roadmap idea by assuming failure and identifying the most credible ways it breaks.
Analyze recurring conflict behavior on software or game projects by identifying likely collaboration patterns, project risks, and practical response strategies. Best for difficult teammate, stakeholder, lead, or founder situations where the real problem is recurring behavior rather than one isolated disagreement.
- Need clarity first ->
game-design-goal-framing - Need more solution paths ->
game-design-option-generationorgame-design-five-options - Need to get unstuck ->
game-design-roadblock-reframingorgame-design-creative-unblocker - Need stronger emotional direction ->
game-design-emotional-canvasorgame-design-fantasy-extractor - Need better psychological diagnosis ->
game-design-player-motivation-audit,game-design-player-need-satisfaction-audit,game-design-attribution-audit, orgame-design-flow-audit - Need to decide what to prototype ->
game-design-unknown-unknowns-prototyping - Need to pick what to do now ->
game-design-feature-prioritization - Need to clarify who the game is really for ->
game-design-player-persona-extractor - Need to extract the real design principles ->
game-design-design-pillars-extractor - Need to isolate the actual repeatable structure ->
game-design-core-loop-extractor - Need to understand why failure feels bad or good ->
game-design-failure-loop-auditorgame-design-fairness-frustration-audit - Need a provocative ambition check ->
game-design-molyneux-lens - Need to audit cognitive demand and mode-switching ->
game-design-thinking-fast-and-slow-audit - Need to audit remembered aftertaste and dominant moments ->
game-design-peak-end-audit - Need to audit unresolved-task tension and return pull ->
game-design-zeigarnik-effect-audit - Need a beginner planning sequence ->
game-dev-first-steps->game-dev-team-gap->game-dev-budget-estimator->game-dev-time-estimator - Need a deadline realism check ->
game-dev-time-estimator
- The GROW-derived skills are mostly workflow skills.
- The motivation and need-satisfaction skills are mostly audit skills.
game-design-creative-unblockeris intentionally sillier and more disruptive than the rest of the pack.