Coding standards, frameworks, refactoring, and code review (17K skills)
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
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.