donchitos/claude-code-game-studios
4 skills4 installs84.8k starsGitHub
Install
npx skills add https://github.com/donchitos/claude-code-game-studiosSkills in this repo
1Bug TriageBug Triage is an agent skill for solo builders and small game-studio style teams who keep bugs as markdown under production/qa/bugs/. At sprint start, after QA filing waves, or once open items cross roughly ten, you invoke it to scan every open report, re-score impact (severity) against urgency (priority), assign fixable work to the active sprint or backlog, and call out repeating failure patterns before they become release blockers. Optional arguments choose sprint-focused assignment, a full-backlog pass, or trend-only analysis without changing assignments. Allowed tools are read/search plus write/edit so the agent can produce an auditable triage artifact teammates can execute against. It pairs naturally with structured QA workflows that file individual bug markdown files rather than ad-hoc chat threads.1installs2Code ReviewCode Review for Claude Code Game Studios is an agent skill that turns ad-hoc “look at this file” chat into a repeatable architectural review for solo game developers using a pinned engine workflow. You invoke it with a path (and optionally a story markdown path) so the agent loads CLAUDE.md standards, discovers ADR references from the story or file headers, and delegates engine-specific concerns to specialists declared in technical-preferences. It evaluates compliance with your chosen patterns, SOLID boundaries, testability, and performance—not just style nits—before you merge combat systems, UI flows, or shaders. When engine specialists are still `[TO BE CONFIGURED]`, the skill gracefully skips engine routing and stays at project-level review. It fits indie pipelines that already track epics and ADRs but want the coding agent to enforce them consistently.1installs3Design SystemDesign-system is an agent skill for indie and solo game studios who need disciplined game design documents without dumping a wall of text in one shot. Invoked as `/design-system <system-name>` with optional `--review full|lean|solo`, it validates arguments, loads review mode once per run, and either designs the requested system or prompts from `design/gdd/systems-index.md` for the next not-started system. It gathers context from existing GDD files, walks each required section collaboratively, cross-references dependent systems, and writes updates incrementally using Write and Edit. TodoWrite and Task support longer authoring sessions. The workflow aligns with director-gates documentation for quality checks at each stage. It fits builders using Claude Code with filesystem access to a `design/gdd/` tree who treat systems as first-class design units before or during implementation.1installs4Perf Profileperf-profile is a structured performance profiling workflow for solo and indie game studios using Claude Code with a dedicated performance-analyst agent. You invoke it with a system name to focus on one subsystem or with full for a comprehensive pass across CPU, memory, and rendering surfaces. The skill first aligns work to documented budgets such as 60 FPS frame time, per-system memory caps, load-time targets, and draw-call limits, then systematically hunts bottlenecks in update loops, allocations, asset footprints, and render paths. It is meant for builders who already have runnable code and need prioritized optimization guidance instead of ad-hoc guessing. Bash, Read, Glob, and Grep access let the agent inspect the real codebase rather than theorize. Use it when performance regressions block milestones, when you are approaching a demo or store submission, or when you need a repeatable audit trail before cutting scope or rewriting hot paths.1installs