Updated 4mo ago
by fagemx
gstack-game
Complete game production workflow for Claude Code — 27 skills from concept to shipped build. Design review, prototype planning, game feel diagnosis, playability assessment, QA with fix loop, and release. Built on gstack methodology.
73 GitHub stars (73)
+2 in 16 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | −1 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 0 |
| Oct 9 | +2 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | 0 |
| Oct 14 | 0 |
| Oct 15 | +1 |
| Oct 16 | 0 |
- 30 skills (30 skills found in its SKILL.md files)
- 10 forks (10 forks)
- 4mo ago last update (Last updated 4mo ago)
Install
Skills CLI
npx skills add fagemx/gstack-game
Asks which skills and agents to install. Just one: npx skills add fagemx/gstack-game --skill gstack-game — add -g for every project.
Claude Code
git clone https://github.com/fagemx/gstack-gamecp -r "gstack-game" ~/.claude/skills/gstack-game
Copies the gstack-game skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add fagemx/gstack-game
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 — showing the first 30 of 37 files.
-
gstack-game
Game development workflow skills for Claude Code. 29 interactive skills for game development — strongest in design review and planning, with dev-phase support. When you notice the user is at these stages, suggest the appropriate skill: - User has a fragile mood/image/mechanic fragment and wants creative sparks, not critique → suggest /spark-lens - User has a PDF/doc/notes they want to turn into a…
SKILL.md on GitHub (opens in a new tab) -
asset-review
Asset pipeline QA. Checks naming conventions, file formats, performance budgets, style consistency (deviation counting, not quality judgment), and pipeline health. Use when you have game assets to audit — NOT for in-engine visual review (use /game-visual-qa) or architecture review (use /game-eng-review).
skills/asset-review/SKILL.md on GitHub (opens in a new tab) -
balance-review
Use when a game has numbers that need checking — difficulty curves, currency flow, gacha rates, progression pacing, grind ratios, or pay-to-win concerns. Not for visual design, narrative, core loop evaluation (use /game-review), or player experience walkthrough (use /player-experience).
skills/balance-review/SKILL.md on GitHub (opens in a new tab) -
build-playability-review
Use when a prototype or build exists and you need to know: is this worth playing? Not QA (use /game-qa for bugs), not feel (use /feel-pass for responsiveness), not code (use /gameplay-implementation-review). This evaluates the EXPERIENCE: does the loop close, does the session hold, does the player want to come back.
skills/build-playability-review/SKILL.md on GitHub (opens in a new tab) -
careful
Safety mode. Warns before destructive commands (rm -rf, DROP TABLE, git push -f, force delete). Does NOT restrict file editing scope — use /guard for that.
skills/careful/SKILL.md on GitHub (opens in a new tab) -
feel-pass
Use when a prototype or playable build exists and you need to know if a mechanic feels alive or dead — responsiveness, impact, rhythm, feedback chains, dead time. Not for GDD review (use /game-review), not for code review (use /gameplay-implementation-review), not for bug hunting (use /game-debug). Requires a playable build or detailed video of gameplay.
skills/feel-pass/SKILL.md on GitHub (opens in a new tab) -
game-codex
Adversarial second opinion for game code and design. Independent review from a fresh context, focused on game-specific failure modes. 3-pass exploit methodology (attack surface → systematic scan → creative exploitation), design challenge with fallacy detection, and structured consulting.
skills/game-codex/SKILL.md on GitHub (opens in a new tab) -
game-debug
Game debugging and root cause analysis. Analyzes crash dumps, performance bottlenecks, physics glitches, network desync, and gameplay bugs through structured hypothesis testing.
skills/game-debug/SKILL.md on GitHub (opens in a new tab) -
game-direction
Game direction review from producer/creative director perspective. Challenges premises, evaluates scope, market positioning, and strategic alignment.
skills/game-direction/SKILL.md on GitHub (opens in a new tab) -
game-docs
Game release documentation update. Generates player-facing patch notes, internal changelog, and updates all project documentation after a release.
skills/game-docs/SKILL.md on GitHub (opens in a new tab) -
game-eng-review
Game technical architecture review. Evaluates engine choice, rendering pipeline, networking, physics, data persistence, and platform adaptation.
skills/game-eng-review/SKILL.md on GitHub (opens in a new tab) -
game-ideation
Interactive game concept brainstorming. Structures raw ideas into Fantasy/Loop/Twist, challenges assumptions with forcing questions, and validates with Iceberg framework.
skills/game-ideation/SKILL.md on GitHub (opens in a new tab) -
game-import
Import and standardize game design documents from any format (PDF, Notion export, Google Doc, chat logs, verbal description) into the gstack-game standard markdown structure at docs/gdd.md. Gateway skill — run this first before /game-review or any other review skill.
skills/game-import/SKILL.md on GitHub (opens in a new tab) -
game-qa
Systematic game QA. Tests functional correctness, visual quality, performance, audio, input, compatibility, localization, and progression integrity.
skills/game-qa/SKILL.md on GitHub (opens in a new tab) -
game-retro
Game development sprint/milestone retrospective. Tracks feature completion, bug density trends, velocity, and team health with quantitative metrics.
skills/game-retro/SKILL.md on GitHub (opens in a new tab) -
game-review
Trigger: User wants a structured review of a Game Design Document (GDD). Use when: "review my GDD", "game review", "check my game design", "how's my GDD", "/game-review", or user has a docs/gdd.md and asks for design feedback. Do NOT use when: User wants code review (use /review), balance-specific analysis (use /balance-review), or brainstorming from scratch (use /game-ideation).
skills/game-review/SKILL.md on GitHub (opens in a new tab) -
game-ship
Game release workflow. Build, test, changelog, PR, platform submission. Supports Steam, App Store, Google Play, Web, and custom pipelines.
skills/game-ship/SKILL.md on GitHub (opens in a new tab) -
game-ux-review
Game UI/UX review. Evaluates HUD readability, menu flow, shop interface, tutorial UI, controller/touch adaptation, and accessibility.
skills/game-ux-review/SKILL.md on GitHub (opens in a new tab) -
game-visual-qa
Visual QA for games. Reviews art style consistency, UI alignment, animation quality, screen adaptation, and visual polish.
skills/game-visual-qa/SKILL.md on GitHub (opens in a new tab) -
gameplay-implementation-review
Use when a PR or code change exists for a game project and you need to review it for both code quality AND design intent survival. Evolved from /game-code-review — adds Pass 0 checking whether design intent from handoff survived implementation. Not for reviewing design docs (use /game-review), not for feel evaluation (use /feel-pass), not for playability (use /build-playability-review).
skills/gameplay-implementation-review/SKILL.md on GitHub (opens in a new tab) -
guard
Full safety mode. Combines /careful (destructive command warnings) with file scope restriction. Prevents editing files outside a specified directory.
skills/guard/SKILL.md on GitHub (opens in a new tab) -
implementation-handoff
Use when a prototype slice plan exists and you need to translate design intent into a build package that a coding agent or developer can execute. Not for deciding what to build (use /prototype-slice-plan), not for reviewing built code (use /gameplay-implementation-review), not for evaluating architecture (use /game-eng-review).
skills/implementation-handoff/SKILL.md on GitHub (opens in a new tab) -
pitch-review
Game pitch/proposal review — triggered when user has a game concept, pitch deck, or GDD to evaluate. Scores market positioning, differentiation, feasibility, business case, and pitch quality. Outputs a weighted Pitch Health Score with GREENLIGHT / PROTOTYPE FIRST / PIVOT / PASS recommendation.
skills/pitch-review/SKILL.md on GitHub (opens in a new tab) -
plan-design-review
Designer's eye plan review for games. Rates 7 design dimensions 0-10, explains what a 10 looks like, then fixes the plan to get there. Use when a game plan exists but UI/UX decisions need to be specified before implementation. Proactively suggest when the user has a plan with UI components that should be reviewed before building.
skills/plan-design-review/SKILL.md on GitHub (opens in a new tab) -
player-experience
First-person player experience walkthrough — simulates playing the game as a specific persona, narrating moment-by-moment what the player sees, feels, and does. Use when you want to find friction, confusion, and churn risks through role-play rather than analysis.
skills/player-experience/SKILL.md on GitHub (opens in a new tab) -
playtest
Playtest protocol design. Creates test plans, defines observation metrics, structures feedback collection, and designs data analysis frameworks.
skills/playtest/SKILL.md on GitHub (opens in a new tab) -
prototype-slice-plan
Use when design review is done and you need to decide what to build FIRST — which slice, what hypothesis to test, what to fake, what failure looks like. Not for brainstorming (use /game-ideation), not for reviewing a GDD (use /game-review), not for handing off to implementation (use /implementation-handoff after this skill).
skills/prototype-slice-plan/SKILL.md on GitHub (opens in a new tab) -
spark-lens
Low-pressure creative spark facilitation for early game ideas. Use when the user wants to protect enthusiasm, explore a half-formed concept, turn a feeling, image, character, mechanic, dream, or unfinished fragment into richer game possibilities, or leave an emotional imprint on the project before formal ideation/review. Avoid scoring, critique, feasibility checks, market language, investment lan…
skills/spark-lens/SKILL.md on GitHub (opens in a new tab) -
triage
Entry point for new users. Detects project state from existing artifacts, asks 0-2 targeted questions, and routes to the right skill. Run this when you don't know which gstack-game skill to start with.
skills/triage/SKILL.md on GitHub (opens in a new tab) -
unfreeze
Deactivate /guard scope restriction. Returns to normal editing mode.
skills/unfreeze/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.