Coding standards, frameworks, refactoring, and code review (16.9K skills)
Implement a planned game development task by gathering its specifications and design decisions, then assigning the right programming specialist. Coordinate source changes, tests where required, visual evidence, and session state for subsequent review and closure.
Find the next step in a game development project by checking workflow records, existing documents, and task status. Get one main recommendation with a command, plus a brief view of completed work and upcoming tasks.
View and change shared project settings and personal overrides without editing YAML manually. See which values actually apply, where they come from, which allow personal overrides, and which are stored without affecting behavior.
Handle critical bugs in a released game through an emergency workflow. Investigate the cause, prepare a minimal fix, track reviews and tests, and verify the fix reaches development branches, with deployment approval and post-release checks recorded.
Audit an existing project's design documents and supporting files to check whether their formats work with the template's skills. Get a numbered migration plan that prioritizes gaps and required changes, rather than simply listing what exists.
Turn small game changes into concise specifications with clear reasons, rules, and acceptance criteria. Check existing design documents and earlier specifications, then document tuning adjustments, minor behavior changes, or small features before implementation.
Translate approved game designs into a technical blueprint before coding begins. Map system layers, module responsibilities, data flow, and API boundaries, then check architecture decisions against the pinned engine and identify missing knowledge or decisions.
Assess a game project's development stage by examining design documents, code, tests, and planning files. Identify gaps appropriate to its workflow, compare findings with the configured stage, and recommend next steps for different team roles.
Prepare and check a game's localization, from extracting text and briefing translators to checking missing translations and display limits. It also covers cultural review, voice recording preparation, right-to-left layouts, and release quality checks.
Break a game concept into the systems it needs, including supporting systems that are easy to overlook. Map dependencies, assign priorities by development stage, and create an index showing the recommended order for detailed design.
Review whether game design requirements are covered by documented architecture decisions. Identify missing coverage, conflicting decisions, and engine compatibility concerns, with an optional matrix linking requirements to development stories and tests.
Audit game asset files for naming rules, size limits, formats, and broken references. Receive a report of measured violations and suggested fixes, with clear explanations of checks that lack data or cannot be assessed for the engine.
Write a game design document for one system, such as combat, crafting, or dialogue. Work through sections with specialist agent input, check dependencies against existing designs, and save approved sections with progress records for later continuation.
Create realistic sample data for testing, development, and demos. Specify fields, record counts, value ranges, and business rules, then receive CSV, JSON, SQL INSERT statements, or a Python generator script with validation and usage instructions.
Review code changes or a repository for actionable bugs by tracing how components interact. Findings explain reachable triggers, incorrect behavior, consequences, and checked counterarguments. Correctness is the default focus; performance and security can also be selected.
Extract code and resources from installed Electron apps to inspect how they are built. Restore original files when source maps contain them, or format compressed JavaScript for easier reading. Supports app discovery on macOS and Windows.
Improve a measurable target in a working system by tracing workload costs or scoring alternative implementations. Compare results against a baseline, keep confirmed improvements on a dedicated branch, and record experiments for review or resumption.
Turn recorded product feedback from screens, voice, or notes into evidence for bug reports and requirements. Handle a single issue quickly or organize a broader evidence set, and guide Riffrec installation, capture, and sharing when no recording exists.
Turn a vague feature idea into clear requirements through dialogue. Define what to build, its scope, and success criteria, then capture the result in a short chat summary or a requirements document ready for implementation planning.
Commit and push code changes, then open a pull request with a clear title and description. You can also draft or update PR descriptions and hand published requests to the follow-up monitoring workflow.
Check the Compound Engineering environment and repository settings, identify configuration issues, and report optional tools. Confirm where generated documents will be stored, make approved configuration fixes, or scaffold a Compound Pack with pack:<id>.
Investigate errors, failing tests, or slow behavior and explain the causal chain with source file and line references. Deliver diagnosis alone or apply a verified fix, starting with a test that reproduces the defect.
Refine a working feature through browser feedback from the user. Collect observations through typed comments or live speech and drawing, apply focused usability fixes, and save the changes in local commits.
Set up a separate Git working directory for a new task or an existing branch, pull request, or commit. Detect and reuse existing isolation, prefer the agent environment's worktree tools, and report the working path and branch.