개발 스킬

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a ready game development story
• Assigning implementation to the right programming specialist
• Collecting required tests and visual evidence

Review game code for likely performance bottlenecks in processing, memory, rendering, and data loading. Compare available estimates with configured limits and produce ranked optimization recommendations, including expected impact, effort, risks, and areas needing runtime measurement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding performance bottleneck candidates in one game system
• Reviewing performance across the whole game
• Comparing available estimates with configured performance limits

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking image and audio naming conventions
• Finding files that exceed asset size limits
• Investigating missing references and potentially unused assets

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find game requirements without architecture decisions
• Check for conflicts between architecture decisions
• Review compatibility with the pinned engine version

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a technical blueprint before implementation
• Clarifying system layers and module responsibilities
• Mapping data flow and API boundaries

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Identifying the systems a game concept requires
• Finding dependency cycles and bottleneck systems
• Choosing systems for the minimum playable version

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find hardcoded text and prepare translation tables
• Check missing translations and placeholder mismatches
• Prepare translator briefs and voice recording scripts

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting game balance adjustments
• Specifying minor behavior changes
• Defining a small mechanic for an existing system

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understanding the state of an inherited game project
• Getting oriented when joining a development team
• Checking gaps before a milestone

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking effective settings and their sources
• Changing settings shared by the team
• Applying personal overrides

Check game design documents against a shared registry of entities, items, formulas, and constants. Get a report of conflicting values, outdated registry entries, and references that lack enough detail to verify, with guidance on which documents need changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking consistency after adding a game design document
• Finding conflicting item prices or attributes
• Reviewing documents changed since the last review

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Responding to crashes or data loss in a released game
• Preparing a minimal emergency patch
• Tracking patch approvals, tests, and rollback plans

Trace changes in a game design document to related architecture decision records, which explain technical choices. Compare their assumptions with the revised design, report which decisions need review, and guide updates to decisions and requirement links.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking architecture impact after changing game design
• Finding technical decisions based on outdated requirements
• Choosing whether to keep, revise, or replace a decision

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing changes for bugs before integration
• Investigating state mismatches across components
• Checking whether a fix introduces another defect

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating test data that follows business rules
• Preparing realistic sample data for demos
• Populating a test database

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Inspecting code bundled in an Electron app
• Restoring source files from source maps
• Formatting compressed JavaScript for reading

Review and simplify code while preserving its behavior. Check readability, reuse, and efficiency, assess whether tests and comments add value, and verify applied changes with the project's configured checks before review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Cleaning up code after implementation
• Improving readability before code review
• Auditing tests for practical value

Carry a request through the appropriate Compound Engineering skills with minimal intervention. For code changes, the workflow covers planning, implementation, review, browser testing, and an open pull request with automated check results assessed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Taking a feature request through to an open pull request
• Diagnosing a bug and preparing the fix for review
• Implementing an existing plan through delivery

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Refining usability before release
• Adjusting a page while checking the changes
• Giving feedback through speech and on-page drawing

Address existing feedback on a GitHub pull request, a proposed code change. Evaluate comments against the code, apply valid fixes, and verify replies and thread resolution, with options for local handoff or resuming saved work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Addressing feedback across a pull request
• Handling a specific review thread
• Preparing local fixes for someone else to publish

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trace the cause of an error or failing test
• Investigate unexpectedly slow behavior
• Get a diagnosis before deciding on a fix

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Committing changes and opening a pull request
• Drafting only a PR title and description
• Updating an existing PR description

Review code changes or a pull request for bugs, effects on existing behavior, test gaps, and project standards. Receive findings supported by the code and a clear account of review coverage, with local fixes available when explicitly requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a pull request before release
• Checking changes for bugs and test gaps
• Applying review findings locally

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating the cost of a specific workload
• Comparing implementations against a measurable target
• Running improvement experiments within time and spending limits