Game Design Review
Reviews an existing GDD or feature spec with a severity-rated rubric: pillar alignment, MDA and player-psychology fit, consistency, scope, testability for agent-built games, originality, AI disclosure and accessibility hooks, ending in a build-readiness verdict. Use for "review my GDD", "design feedback", "critique this spec". Not for writing a GDD (use game-gdd-author).
Install
/plugin marketplace add AlterLab-IEU/AlterLab_GameForgeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-design-reviewgit clone --depth 1 https://github.com/AlterLab-IEU/AlterLab_GameForge.git /tmp/AlterLab_GameForge
mkdir -p ~/.claude/skills
cp -r /tmp/AlterLab_GameForge/skills/workflows/game-design-review ~/.claude/skills/game-design-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# AlterLab GameForge -- Design Document Review A game design document is a contract between ambition and execution capacity. A bad GDD is not badly formatted; it is one that lets the team build confidently in the wrong direction for weeks before anyone notices. Most fail because they describe a game without constraining it: anything goes, so nothing coheres. This is not a checklist review. A checklist confirms sections exist. This review confirms they are good: internally consistent, psychologically grounded, scope-honest, and specific enough to drive implementation. In 2026 that last test is literal. When a GDD section goes to Claude Code or a similar agent, every vague sentence becomes a guess in code, so this review also asks: **could an agent build this, and could a test tell whether it built it right?** And because players, stores and regulators now care how a game was made, it checks originality, AI-content disclosure and accessibility while changes are still cheap. ## When to Use / When Not To Use before implementation starts, as a gate before a section is handed to a coding agent, after significant design changes, when a playtest went badly and the cause may be in the design, or when the team disagrees about what the game is. | Instead of this skill... | Use | |---|---| | Writing or rebuilding GDD sections | `/gameforge:game-gdd-author` | | Generating new ideas | `/gameforge:game-brainstorm` |
Details
- Skill name
game-design-review- Repository
- AlterLab-IEU/AlterLab_GameForge
- Path
skills/workflows/game-design-review/SKILL.md- License
- MIT
- Repo updated
- 6 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Game Design Review skill do?
Reviews an existing GDD or feature spec with a severity-rated rubric: pillar alignment, MDA and player-psychology fit, consistency, scope, testability for agent-built games, originality, AI disclosure and accessibility hooks, ending in a build-readiness verdict. Use for "review my GDD", "design feedback", "critique this spec". Not for writing a GDD (use game-gdd-author).
How do I install the Game Design Review skill?
Claude Code plugin: /plugin marketplace add AlterLab-IEU/AlterLab_GameForge. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Game Design Review popular?
It lives in AlterLab-IEU/AlterLab_GameForge, which has 57 GitHub stars and 6 forks, and is included in 1 curated skill list.
Related skills
Game Accessibility Specialist
57AlterLab-IEU/AlterLab_GameForge
Accessibility Specialist (Kael Oduya). Designs motor, visual, auditory and cognitive accommodations, runs accessibility audits, scopes the European Accessibility Act, CVAA and Game Accessibility Guidelines, and maps fixes to Godot, Unity, Unreal or web. Use for "accessibility audit", "EAA", "colorblind", "subtitles", "remapping". Not for general UX flows (use game-ux-designer).
Game AI Assets
57AlterLab-IEU/AlterLab_GameForge
Runs an AI-assisted asset pipeline for models, sprites, textures, audio and voice: generate vs make vs buy, license-first tool choice, style lock, engine post-processing, and a per-asset provenance log for Steam, itch.io and EU AI Act disclosures. Use for "generate a sprite with AI", "ElevenLabs", "can I ship this AI asset". Not for defining art style (use game-art-director).
Game Analytics Setup
57AlterLab-IEU/AlterLab_GameForge
Sets up privacy-first game analytics: question-driven event taxonomies, consent-gated telemetry (GDPR, COPPA, ATT), engine and web SDK choice, KPI definitions, dashboards, A/B tests, and AI feedback summaries validated against real data. Use for "analytics", "telemetry", "KPIs", "retention", "funnel", "A/B test". Not for balance tuning (use game-balance-check).
Game Gdd Author
57AlterLab-IEU/AlterLab_GameForge
Guides section-by-section writing of a game design document that doubles as an agent-verifiable spec: pillars, core loop, MDA-tagged systems with pass/fail acceptance criteria and tuning knobs, scope tiers and an AI-use policy. Use for "write my GDD", "create a game design document", "turn my concept into a spec". Not for critiquing an existing GDD (use game-design-review).
Game Brainstorm
57AlterLab-IEU/AlterLab_GameForge
Runs designer-led ideation that turns a mood, theme, genre or "something like X" into three original concepts and one chosen Game Concept Document with core loop, pillars, player fit and scope, plus 5-10 minute web or jam hooks. Use for "game idea", "brainstorm", "pitch", "what should I make", "a game like X". Not for market sizing (use game-market-research).
Game Help
57AlterLab-IEU/AlterLab_GameForge
Start-here guide to GameForge: maps the user's goal, project phase and engine to the right skill or skill chain, and explains the studio agents, hooks and project config. Use for "what can GameForge do", "which skill should I use", or when unsure how to approach a game-dev task. Not for setting up a project (use game-start).
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.