unity-code-reviewThis skill should be used when the user asks to review Unity code, requests a code review, wants to check code before merging, or says 'review my changes', 'check this before merge', 'run a code review', or 'what should I look for in review'. Covers requesting review via a code-reviewer subagent, re
unity-ecs-patternsThis skill should be used when the user is working with Unity DOTS — Entity Component System, Job System, or Burst Compiler. Trigger phrases include "ECS", "DOTS", "ISystem", "IJobEntity", "entity component system", "SystemAPI", "EntityQuery", "entity command buffer", "ECB", "baking", "authoring com
unity-executing-plansThis skill should be used when the user asks to execute, implement, or follow a Unity implementation plan. Common triggers include 'execute the plan', 'implement the plan', 'start building from the plan', 'run the tasks in the plan', or 'follow the plan step by step'. Handles batch execution of plan
unity-exploring-projectThis skill should be used when the user wants to design or plan a new Unity feature, system, or behavior before writing code. Trigger phrases include 'I want to build', 'design a system for', 'let us add a feature', 'plan out', 'how should I architect', 'I need a new system', 'create a feature for'.
unity-finishing-branchThis skill should be used when the user says 'I'm done with this feature branch', 'merge my work back', 'finish this branch', 'create a PR for this', 'ready to merge', 'wrap up this branch', 'clean up and merge', or 'discard this branch'. Runs full Unity verification, resolves Unity-specific pre-mer
unity-subagent-devThis skill should be used when the user wants to execute an implementation plan by dispatching independent tasks to subagents, with spec compliance and code quality reviews after each task. Relevant when the user says 'execute my plan with subagents', 'implement these tasks one at a time', 'run my p
unity-systematic-debuggingThis skill provides a systematic four-phase debugging process for Unity projects. It should be used when the user encounters a Unity bug, NullReferenceException, test failure, unexpected runtime behavior, compile error, build failure, or performance problem. Trigger phrases include 'debug this', 'fi
unity-tddThis skill should be used when the user asks to write tests first, do TDD, implement a feature or bugfix using test-driven development, add unit tests before coding, write EditMode or PlayMode tests, or set up Unity Test Runner. Also applies when a user says 'red green refactor', 'write a failing te
unity-verificationThis skill should be used when a user asks to verify Unity work, confirm tests pass, check that a bug is fixed, validate a build, finalize a task, or mark work as complete. Trigger phrases include 'verify this works', 'run the tests', 'is this done', 'check the build', 'confirm it compiles', 'mark t
unity-writing-plansThis skill should be used when the user wants to write an implementation plan, create a task breakdown, or plan out a Unity feature before writing code. Trigger phrases include: 'write a plan', 'create a plan', 'plan this feature', 'break this into tasks', 'implementation plan', 'plan before coding'
using-superunityThis skill should be used when starting any conversation involving Unity 3D game development, C# scripting, MonoBehaviour, ScriptableObject, or Unity Editor workflows. It establishes the skill discovery and invocation process for all Unity tasks. Relevant when the user says things like "help me buil