Updated 4mo ago
by baxatron-git
claude-game-design-suite
22-skill game design framework for Claude Code. Full lifecycle coverage — vision to delivery. Medium-agnostic
21 GitHub stars (21)
+1 in 3 days
| Period | New stars |
|---|---|
| Nov 15 | 0 |
| Nov 16 | +1 |
| Nov 17 | 0 |
- 22 skills (22 skills found in its SKILL.md files)
- 1 forks (1 forks)
- 4mo ago last update (Last updated 4mo ago)
Install
Skills CLI
npx skills add baxatron-git/claude-game-design-suite
Asks which skills and agents to install. Just one: npx skills add baxatron-git/claude-game-design-suite --skill aesthetic-direction-framework — add -g for every project.
Claude Code
git clone https://github.com/baxatron-git/claude-game-design-suitecp -r "claude-game-design-suite/aesthetic-direction-framework" ~/.claude/skills/
Copies the aesthetic-direction-framework skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add baxatron-git/claude-game-design-suite
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
aesthetic-direction-framework
Define the sensory identity of a game — how it looks, sounds, and feels in service of the vision and pillars. The bridge between design intent and sensory execution. Use this skill when: (1) establishing the visual, audio, and tactile identity for a new project, (2) a game "feels wrong" and the sensory layer may be misaligned with mechanics or vision, (3) pillar changes require aesthetic re-evalu…
aesthetic-direction-framework/SKILL.md on GitHub (opens in a new tab) -
core-loop-designer
Define the fundamental action cycle — what the player does repeatedly and why it stays engaging. The heartbeat of the game. Use this skill when: (1) translating pillars and experience targets into a concrete gameplay cycle, (2) diagnosing why a game feels repetitive or disengaging, (3) designing nested loop structures (moment-to-moment, session, meta/campaign), (4) identifying attrition risk poin…
core-loop-designer/SKILL.md on GitHub (opens in a new tab) -
design-coherence-engine
Meta-skill that wraps the Game Design Skill Suite (21 skills, 8 tiers). Manages change propagation, coherence checking, priority arbitration, and adaptive flow between game design skills. Use this skill when: (1) starting a new game design project and determining which skills to activate, (2) a design change in one area may affect other areas, (3) checking whether all design elements are still al…
design-coherence-engine/SKILL.md on GitHub (opens in a new tab) -
design-iteration-tracker
Track what changed, why it changed, and what the result was. Prevent circular design and build institutional memory. Use this skill when: (1) logging design decisions with rationale and supporting data, (2) detecting when a proposed change moves back toward a previously rejected state, (3) tracking the impact chain of changes across systems, (4) maintaining version history of key design parameter…
design-iteration-tracker/SKILL.md on GitHub (opens in a new tab) -
design-pillars-architect
Distill a game vision into 3-5 actionable design pillars that constrain and guide every design decision. Pillars are the filter — if a feature doesn't serve a pillar, it gets cut. Use this skill when: (1) a game vision exists but needs translating into actionable constraints, (2) the team needs a shared framework for evaluating design decisions, (3) feature creep threatens and the project needs r…
design-pillars-architect/SKILL.md on GitHub (opens in a new tab) -
economy-progression-designer
Design the mathematical backbone of a game — resource flows, power curves, unlock pacing, and reward schedules. Use this skill when: (1) designing resource systems (currencies, materials, energy, cards, tokens), (2) defining progression curves (XP, power, unlock cadence), (3) choosing reward schedules (fixed, variable, interval-based), (4) diagnosing inflation, deflation, or resource starvation,…
economy-progression-designer/SKILL.md on GitHub (opens in a new tab) -
game-balance-analyst
Ensure meaningful choice — no dominant strategies, no dead options, no runaway leaders or hopeless laggards. Use this skill when: (1) evaluating whether all player options are viable, (2) identifying dominant strategies that eliminate meaningful choice, (3) designing asymmetric balance (different factions, characters, or roles that feel fair despite being different), (4) building Monte Carlo or s…
game-balance-analyst/SKILL.md on GitHub (opens in a new tab) -
game-market-analyst
Analyze the competitive landscape, identify market positioning, and validate commercial viability of a game concept. The discipline of knowing where your game lives in the market before you build it. Use this skill when: (1) mapping the competitive landscape for a game concept, (2) identifying underserved niches and market gaps, (3) analyzing comparable titles for revenue, audience size, and rece…
game-market-analyst/SKILL.md on GitHub (opens in a new tab) -
game-vision-architect
Define the foundational identity of a game — who it's for, why it should exist, and what fantasy it fulfills. Use this skill when: (1) starting a new game project from scratch, (2) the designer has an idea but hasn't articulated a clear vision, (3) a game needs its core identity defined or redefined, (4) working backward from a mechanic/aesthetic to establish the vision it serves, (5) validating…
game-vision-architect/SKILL.md on GitHub (opens in a new tab) -
gdd-author
Structure and maintain a living Game Design Document — the single source of truth for the game's design. Use this skill when: (1) creating a GDD from existing design outputs, (2) structuring a modular, navigable document that scales with the project, (3) determining appropriate detail level for different audiences (team, publisher, investor), (4) integrating change tracking from iteration history…
gdd-author/SKILL.md on GitHub (opens in a new tab) -
high-concept-pitch-writer
Compress a game vision into communication artifacts — the pitch that sells the game to stakeholders, publishers, players, or your own team. Use this skill when: (1) preparing to pitch a game concept to a publisher or investor, (2) writing a store page, Kickstarter campaign, or press release, (3) aligning a team around a shared understanding of the game, (4) testing whether a vision is focused eno…
high-concept-pitch-writer/SKILL.md on GitHub (opens in a new tab) -
level-encounter-planner
Structure spaces and encounters to deliver on pillars and pacing. The craft of "what happens where and in what order." Use this skill when: (1) designing level layouts, encounter sequences, or scenario structures, (2) building pacing curves (tension/release patterns), (3) defining encounter composition (enemy mix, challenge types, resource pressure), (4) choosing spatial flow models (linear, hub-…
level-encounter-planner/SKILL.md on GitHub (opens in a new tab) -
narrative-systems-designer
Design the systems that deliver narrative — not the story itself, but the machinery of storytelling in the game. Use this skill when: (1) choosing between narrative delivery methods (linear, branching, emergent, environmental, systemic), (2) designing how story and mechanics interact and reinforce each other, (3) building quest/mission/scenario structures, (4) defining player agency within the na…
narrative-systems-designer/SKILL.md on GitHub (opens in a new tab) -
player-experience-modeler
Map the intended emotional journey and psychological engagement model for a game. Defines what the player should feel at each stage of play and what motivates continued engagement. Use this skill when: (1) translating a vision and pillars into concrete emotional targets, (2) designing the pacing of a play session or campaign, (3) evaluating whether a game delivers the intended experience, (4) dia…
player-experience-modeler/SKILL.md on GitHub (opens in a new tab) -
playtest-protocol-designer
Structure playtests to generate actionable data, not just "it was fun" or "it wasn't." Use this skill when: (1) planning a playtest session with clear objectives, (2) designing observation checklists and post-play questionnaires, (3) choosing between playtest types (blind, facilitated, A/B, stress test), (4) building data collection plans (quantitative vs. qualitative), (5) creating analysis fram…
playtest-protocol-designer/SKILL.md on GitHub (opens in a new tab) -
prototype-scope-definer
Define the minimum buildable artifact that tests the core design hypothesis. Prevent over-building before validation. Use this skill when: (1) defining what a prototype must include to test the core hypothesis, (2) making build-vs-fake decisions (what must be real, what can be placeholder), (3) setting aesthetic fidelity targets for a prototype, (4) defining success criteria for prototype validat…
prototype-scope-definer/SKILL.md on GitHub (opens in a new tab) -
rules-formalizer
Write game rules with mathematical precision — unambiguous, complete, edge-case-aware. For tabletop, this IS the game. For digital, this is the systems specification. Use this skill when: (1) translating a core loop and mechanics concepts into precise rule definitions, (2) writing a tabletop rulebook or digital systems spec, (3) identifying and resolving edge cases and rule conflicts, (4) buildin…
rules-formalizer/SKILL.md on GitHub (opens in a new tab) -
scope-feature-prioritizer
Decide what to build and in what order. The skill of cutting the right things. Use this skill when: (1) applying MoSCoW prioritization mapped to design pillars, (2) defining the Minimum Viable Game, (3) building feature dependency graphs (what must exist before what), (4) making risk-weighted priority decisions (high risk = prototype early), (5) managing scope creep by evaluating features against…
scope-feature-prioritizer/SKILL.md on GitHub (opens in a new tab) -
systems-interaction-mapper
Map how all game systems affect each other. Identify feedback loops, emergent behaviors, and potential degenerate strategies before they ship. Use this skill when: (1) designing a game with multiple interacting systems, (2) diagnosing unexpected emergent behavior or exploit paths, (3) evaluating whether adding a new system creates healthy or degenerate interactions, (4) identifying which systems…
systems-interaction-mapper/SKILL.md on GitHub (opens in a new tab) -
technical-design-bridge
Translate game design into implementation requirements without prescribing engineering solutions. The bridge between "what the designer wants" and "what gets built." Use this skill when: (1) translating formalized rules into systems specifications, (2) identifying data structure requirements from game state, (3) flagging performance-critical systems, (4) assessing platform constraints and their d…
technical-design-bridge/SKILL.md on GitHub (opens in a new tab) -
ui-ux-systems-designer
Design the information architecture and interaction model — how the player reads game state and provides input. The interface between the player's brain and the game's systems. Use this skill when: (1) designing information hierarchy (what the player needs to know, in what order), (2) defining input models (how players express intent), (3) designing feedback language (how the game communicates ou…
ui-ux-systems-designer/SKILL.md on GitHub (opens in a new tab) -
world-logic-checker
Keep the fiction internally consistent as the game scales. The rules of the world, not the rules of the game. Use this skill when: (1) establishing the foundational rules of a game's fictional world, (2) checking new content for lore contradictions, (3) tracking implications of world-building decisions ("if X is true, then Y must also be true"), (4) building faction/entity relationship maps, (5)…
world-logic-checker/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.