By Donchitos

Create an ADR documenting a technical decision: context, alternatives considered, consequences.

Donchitos/Claude-Code-Game-Studios

Implement a story: ADR guidelines, right programmer agent, code plus test.

Donchitos/Claude-Code-Game-Studios

Audits game assets against naming conventions, file size budgets and format standards, and finds orphaned assets and missing references.

Donchitos/Claude-Code-Game-Studios

Writes per-asset visual specs and AI image-generation prompts for a game's characters, enemies and screens, driven by the GDD, art bible and an entity inventory.

Donchitos/Claude-Code-Game-Studios

Checks game data and formulas for balance outliers, broken progression, degenerate strategies and economy problems, and answers 'could not run' when the data is missing.

Donchitos/Claude-Code-Game-Studios

Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.

Donchitos/Claude-Code-Game-Studios

Reviews the open bug backlog, separates severity from priority, assigns fixes to sprints and reports systemic trends, writing a dated triage file.

Donchitos/Claude-Code-Game-Studios

Generates an internal or player-facing changelog from git commits and sprint data, filtering out framework maintenance commits so that only work on the game itself reaches release copy.

Donchitos/Claude-Code-Game-Studios

Performs an architectural review of code against coding standards, SOLID, testability and performance, and reports no verdict when the inputs are missing.

Donchitos/Claude-Code-Game-Studios

Compares every game design document against the entity registry to find cross-document conflicts such as differing stats, using a grep-first scan that avoids full reads.

Donchitos/Claude-Code-Game-Studios

Compares the content counts planned in game design documents with what is actually implemented, for one system or the whole project, and reports the gaps.

Donchitos/Claude-Code-Game-Studios

Builds a flat must-do and never-do rules sheet per layer from Accepted architecture decision records and writes it to docs/architecture/control-manifest.md.

Donchitos/Claude-Code-Game-Studios

Turns game design documents and architecture into epics, one per architectural module, ready for story creation in a Claude Code game-studio workflow.

Donchitos/Claude-Code-Game-Studios

Scopes and gates a game's day-one patch after the gold master: fix-only changes, a lightweight QA pass and a rollback plan written before anything ships.

Donchitos/Claude-Code-Game-Studios

Estimates the effort for a game development task from code complexity, scope, risk and past sprint data, returning a range with a confidence level.

Donchitos/Claude-Code-Game-Studios

Reads a game project's current stage and workflow catalog, then tells you which step comes next and which installed skills sit outside the workflow.

Donchitos/Claude-Code-Game-Studios

Runs an emergency fix process for severe bugs: a severity check, a written hotfix record, and a branch cut from the shipped release rather than main.

Donchitos/Claude-Code-Game-Studios

Generates a launch-readiness checklist across code, content, store, marketing, community, infrastructure and legal, scoped to the project and ending in go/no-go sign-offs.

Donchitos/Claude-Code-Game-Studios

Reviews a milestone's completeness, quality metrics and risks and ends with a go or no-go recommendation, stopping when the needed data is missing.

Donchitos/Claude-Code-Game-Studios

Writes an onboarding document for a new contributor or agent, covering project state, conventions and priorities relevant to a chosen role.

Donchitos/Claude-Code-Game-Studios

Writes player-facing patch notes from git history and changelogs, filtering out framework and maintenance commits and rewriting developer wording for players.

Donchitos/Claude-Code-Game-Studios

Finds performance bottlenecks, measures them against frame, draw-call and memory budgets, and ranks the optimization recommendations.

Donchitos/Claude-Code-Game-Studios

Creates a blank playtest report template or converts raw playtest notes into structured findings sorted into design, balance, bug and polish items.

Donchitos/Claude-Code-Game-Studios

Scans a game project to detect its development stage, check artifacts for gaps and recommend next steps, with gap rules that depend on the workflow tier.

Donchitos/Claude-Code-Game-Studios

Finds architecture decision records made stale by a changed game design document, then reports the impact and guides you through resolving each one.

Donchitos/Claude-Code-Game-Studios

Produces a sprint QA plan that classifies stories as logic, integration, visual or UI and sets automated tests, manual checks and smoke scope for each.

Donchitos/Claude-Code-Game-Studios

Writes a short design spec for small gameplay adjustments such as tuning, tweaks and minor additions, and redirects anything larger to a full design document.

Donchitos/Claude-Code-Game-Studios

Maps existing tests to a game's critical paths, finds fixed bugs that lack regression tests and flags coverage drift as new features arrive.

Donchitos/Claude-Code-Game-Studios

Builds a pre-release checklist covering build verification, platform certification, store metadata and launch readiness, trimmed to the project's stage and target.

Donchitos/Claude-Code-Game-Studios

Builds a sprint or milestone retrospective from completed work, velocity and blockers, checking first for an existing retrospective file.

Donchitos/Claude-Code-Game-Studios

Writes the missing GDD section, architecture decision record or concept document by reading existing code and prototypes.

Donchitos/Claude-Code-Game-Studios

Compares the current state of a feature, sprint or milestone with its original plan, flags added scope, quantifies the growth and recommends cuts.

Donchitos/Claude-Code-Game-Studios

Shows or changes a game project's configuration, including merged effective values and per-developer overrides, without hand-editing YAML.

Donchitos/Claude-Code-Game-Studios

Improves a single skill through a test, fix and retest loop, keeping or reverting each change based on how the static and category scores move.

Donchitos/Claude-Code-Game-Studios

Generates the observation protocol and analysis harness for an extended play session that hunts slow memory leaks, performance drift and late-appearing bugs.

Donchitos/Claude-Code-Game-Studios

Creates or updates a sprint plan from the current milestone, completed work and available capacity, sizing the story count to the project's granularity setting.

Donchitos/Claude-Code-Game-Studios

Gives a fast, read-only sprint snapshot with burndown and emerging risks in under 30 lines, plus at most one concrete recommendation.

Donchitos/Claude-Code-Game-Studios

Scans a codebase for debt indicators, sorts findings into six debt categories and maintains a prioritized register you can add to, re-rank and report on.

Donchitos/Claude-Code-Game-Studios

Reviews the quality of test files and evidence documents per story, grading each ADEQUATE, INCOMPLETE, MISSING or NOT ASSESSED rather than only checking they exist.

Donchitos/Claude-Code-Game-Studios

Finds flaky tests in CI logs by aggregating pass rates, explains likely causes and recommends whether to quarantine or fix each one.

Donchitos/Claude-Code-Game-Studios

Generates engine-specific test helper libraries with assertion utilities, factory functions and mocks, placed where the engine's test runner compiles them.

Donchitos/Claude-Code-Game-Studios

Validates a UX spec, HUD design or interaction pattern library for accessibility, design-doc alignment and implementation readiness, ending in one of four verdicts.

Donchitos/Claude-Code-Game-Studios

Checks whether a game project is ready to move to its next production stage and returns a PASS, CONCERNS, NOT ASSESSED or FAIL verdict with blockers.

Donchitos/Claude-Code-Game-Studios

Configures a game project's engine and version, pins them in CLAUDE.md and uses web search to build reference docs when the version is newer than the model knows.

Donchitos/Claude-Code-Game-Studios

Brownfield audit — do existing artifacts actually work?. An agent skill from Donchitos/Claude-Code-Game-Studios.

Donchitos/Claude-Code-Game-Studios

Traceability matrix mapping GDD requirements to ADRs. An agent skill from Donchitos/Claude-Code-Game-Studios.

Donchitos/Claude-Code-Game-Studios

Section-by-section GDD authoring for one system — walks through each required section, cross-references dependencies.

Donchitos/Claude-Code-Game-Studios

Concept prototype before GDDs — throwaway HTML, Engine or Paper build, PROCEED/PIVOT/KILL/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios