개발 스킬

Develop TypeScript services and workflows with Effect v4 by checking its source and existing project examples. Guides data schemas, typed errors, explicit dependencies, and tests that follow the project's established patterns.

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

• Implementing services with Effect v4
• Defining data schemas and typed errors
• Organizing dependencies and HTTP handlers

Keep Kilo-specific changes small in files shared with upstream OpenCode. The skill guides where to place custom logic and tests, how to mark changes, and how to check annotations while preserving behavior.

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

• Add Kilo-specific features to shared upstream code
• Move additive logic into Kilo-owned files
• Clean up outdated or overly broad change markers

Switches the Kilo JetBrains plugin between a pinned released CLI and a freshly built local CLI. Includes commands to clear old build artifacts, regenerate the local executable, and verify the selected setup with Gradle.

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

• Pinning the plugin to the latest stable CLI release
• Switching to a locally built CLI for development
• Regenerating the local CLI after changes

Check whether development tasks are ready for implementation by reviewing acceptance criteria, design decisions, dependencies, and required evidence. Receive one of four verdicts for each task, with specific gaps and suggested fixes.

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

• Checking a task before assigning implementation
• Reviewing all tasks in the current sprint
• Finding ambiguous acceptance criteria

Coordinate a game interface feature from user experience specifications through visual design, implementation, review, and polish. Reuse existing interaction patterns and report input support, accessibility checks, engine validation, and unresolved issues alongside the delivered interface.

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

• Building an inventory screen from specification through implementation
• Designing and implementing a game's main menu
• Creating a HUD with defined visual and interaction constraints

Get started with a game project by reviewing existing work and answering questions about the idea, project scope, and preferred confirmation frequency. Save initial project settings and receive a workflow matched to the chosen level of process.

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

• Starting a game project without an idea
• Choosing next steps for a rough or clear concept
• Organizing existing game documents and code

Refine a game feature or area through performance measurement, visual and audio polish, and stress and regression testing. Report before-and-after metrics, remaining issues, and release readiness, with work limited to the enabled team roles.

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

• Identify performance bottlenecks in combat
• Refine particle effects and shaders
• Review sound feedback and audio mixing

Review a completed development task against its acceptance criteria, check differences from design and architecture documents, and prompt code review. After approval, update the task's status and identify the next story to work on.

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

• Checking acceptance criteria before closing a development task
• Recording differences between implementation and design
• Remembering code review before marking work complete

Find and organize technical debt, the code issues deferred for later improvement. Maintain a register, rank items by impact and repair effort, and report unresolved work and changes over each sprint.

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

• Scan code for signs of deferred maintenance
• Record known issues and reasons for deferring fixes
• Prioritize fixes by impact and effort

Build a short, playable game sequence before full production to check whether the complete gameplay loop works at the intended quality. Use playtest observations and daily progress records to assess feasibility and decide the next direction.

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

• Checking production feasibility after game design is complete
• Testing a complete gameplay loop with players
• Estimating production speed from actual build progress

Coordinate role-based agents to design, implement, integrate, and test a game combat feature. The workflow covers gameplay rules, enemy behavior, visual effects, and audio planning, with a final report on completion, test results, and unresolved issues.

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

• Design and implement a parry mechanic
• Coordinate enemy reactions, effects, and audio events
• Review combat architecture for the configured engine

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

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

Build a quick, disposable game prototype in HTML, a game engine, or on paper to test one core mechanic. Use playtest findings to decide whether to continue, change direction, stop, or leave the idea unassessed.

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

• Test whether a core game mechanic is fun
• Compare several variations of a game concept
• Explore a mechanic change during production

Break a large game development feature into implementation tasks with clear acceptance criteria. Each task carries relevant requirements and design decisions, with test specifications added when the selected review mode includes a QA review.

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

• Break a game feature into implementation tasks
• Carry requirements and design decisions into task files
• Define acceptance criteria and test specifications

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

Improve an existing skill by checking its structure and category requirements, proposing focused fixes, and testing again. Compare failure and warning counts to decide whether to keep changes or restore the previous content.

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

• Fix missing fields and instructions in a skill
• Address findings from category checks
• Compare check results before and after edits

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.

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

• Checking existing documents before adopting a project template
• Auditing game design documents or architecture decision records
• Prioritizing gaps in project tracking and configuration files

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

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.

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

• Finding the next task after a development milestone
• Resuming work from the previous session
• Checking which unfinished task needs attention first

Turn accepted architecture decisions, project preferences, and engine references into a practical rules document. Organize required patterns, forbidden approaches, and performance limits by architectural layer, with a source attached to each rule.

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

• Consolidating implementation rules from accepted decisions
• Updating rules after architecture decisions change
• Reviewing naming conventions and performance limits

Compare planned game content counts with implementation files for enemies, levels, items, abilities, dialogue, and quests. Produce a gap table showing approximate progress and priority shortages, either across all systems or for one selected system.

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

• Comparing planned and implemented game content
• Finding shortages in priority features
• Auditing content for a single game system

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

Review a game design document before implementation. Check missing sections, conflicting rules, formulas, dependencies, and testable success conditions, then report blocking issues and recommended changes. Full mode adds reviews by relevant specialist agents.

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

• Check a design document before implementation
• Find formula errors and conflicting system rules
• Rewrite vague success conditions as measurable checks