IdoCohen560

Unity physics patterns including character controllers, collision handling, and tunneling prevention.

Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.

Unity physics patterns including character controllers, collision handling, and tunneling prevention.

Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

Unity animation patterns including Animancer, state machines, and performance optimization.

Guided, section-by-section Art Bible authoring creates the visual identity specification that gates all asset production. This process runs after /brainstorm is approved and before /map-systems or any GDD authoring begins.

Guided, section-by-section Art Bible authoring creates the visual identity specification that gates all asset production. This process runs after /brainstorm is approved and before /map-systems or any GDD authoring begins.

This skill breaks a single epic into implementable story files, reading the epic, its GDD, governing ADRs, and control manifest, with each story embedding its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

Audits games for security vulnerabilities like save tampering, cheat vectors, network exploits, and data exposure, providing a prioritized report with remediation guidance. Recommended before public release or multiplayer launch.

Generates a QA test plan for a sprint or feature. It reads GDDs and story files to classify stories by test type (Logic/Integration/Visual/UI), producing a structured plan covering automated and manual tests, smoke test scope, and playtest sign-off requirements, to be run before a sprint or major feature.

Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.

Mobile-specific Unity optimization patterns for memory, battery, thermal, and performance.

Moves assets at specified paths in the project, intended for renaming, and performs an AssetDatabase.Refresh(). Use 'assets-find' to locate assets first.

Deletes the script file(s), performs AssetDatabase.Refresh() and waits for Unity compilation to complete before reporting results. Use the 'script-read' tool to read existing script files first.

A guide to the Unity 6 Cinemachine camera system, covering virtual cameras, blending, follow cameras, FreeLook, camera shake, and state-driven cameras. It details the Cinemachine 3.x API, based on Unity 6.3 LTS documentation.

Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.

Duplicate GameObjects in an opened Prefab or in a Scene. Use the 'gameobject-find' tool to find the target GameObjects first.

Translates approved GDDs and architecture into epics, one per architectural module. It defines scope, governing ADRs, engine risk, and untraced requirements, but does not break them into stories; run /create-stories [epic-slug] after each epic is created.

Behavior Designer patterns for AI behavior trees, covering task creation, shared variables, conditionals, and debugging.

Get information about the current Selection in the Unity Editor. Use 'editor-selection-set' tool to set the selection.

Unity scene and asset architecture decisions, covering additive scene composition, Addressables vs Resources, AssetReference workflow, asset lifecycle coordination, and loading screens. It uses the DECISION format (WHEN/DECISION/SCAFFOLD/GOTCHA) and is based on Unity 6.3 LTS.

Generates a soak test protocol for extended play sessions. It defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play, primarily used in Polish and Release phases.

Brownfield onboarding audits existing project artifacts for template format compliance, classifies gaps by impact, and produces a numbered migration plan. Use this when joining an in-progress project or upgrading from an older template version, specifically checking if existing artifacts will work with the template.

Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.

Validates the completeness and consistency of the project architecture against all GDDs. It builds a traceability matrix mapping technical requirements to ADRs, identifies gaps, detects conflicts, verifies engine compatibility, and produces a PASS/CONCERNS/FAIL verdict. This is the architectural equivalent of /design-review.

Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.

Generates per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles, producing structured spec files and updating the master asset manifest. This runs after art bible and GDD/level design approval, before production begins.

Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design.

Guided game concept ideation, from zero idea to a structured game concept document. It employs professional studio ideation techniques, player psychology frameworks, and structured creative exploration.

Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.

Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.

Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.

Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.

Scans all GDDs against the entity registry to detect cross-document inconsistencies, such as the same entity with different stats, item with different values, or formula with different variables. It employs a grep-first approach, reading the registry and targeting only conflicting GDD sections rather than full document reads.

Audits GDD-specified content counts against implemented content, identifying what's planned versus built.

Guides the section-by-section authoring of the game's master architecture document. It reads all relevant development documents and the engine reference library to create a complete architecture blueprint, validating decisions against the pinned engine version.

After architecture is complete, this skill produces a flat, actionable rules sheet for programmers, detailing what to do and what not to do per system and layer. These rules are extracted from Accepted ADRs, technical preferences, and engine reference docs, offering more immediate actionability than ADRs.

Prepares a day-one patch for a game launch, addressing known issues discovered after gold master but before or immediately after public launch. The patch is treated as a mini-sprint with its own QA gate and rollback plan.

Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.

Guided, section-by-section GDD authoring for a single game system. It gathers context from existing documents, collaboratively walks through each required section, cross-references dependencies, and writes incrementally to file.

Reads a story file and implements it by loading the full context (story, GDD, ADR, control manifest), routing to the correct programmer agent, implementing code and tests, and confirming acceptance criteria. This core skill runs after /story-readiness and before /code-review and /story-done.

Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.

Validates readiness to advance between development phases. It produces a PASS/CONCERNS/FAIL verdict, detailing specific blockers and required artifacts, useful for gate checks and phase transitions.

Analyzes what has been done and the user's query, offering advice on next steps. Use if the user says 'what should I do next', 'what do I do now', 'I'm stuck', or 'I don't know what to do'.

Complete launch readiness validation, covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.

A comprehensive localization pipeline that scans for hardcoded strings, manages string tables, validates translations, conducts cultural/sensitivity reviews, handles VO localization, tests platform requirements, enforces string freezes, and reports coverage.

Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index.

Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.