Unity Operation Wizard

Problem

Unity editor windows, components, and settings are spread across many places. A user may only describe a goal or symptom, such as an object not being visible or an animation not playing, without knowing whether to inspect Inspector, Rigidbody, Lighting, or Console. Searching documentation often returns conceptual explanations instead of the exact panel, property, or menu entry for the current editor version.

How It Works

The skill treats questions as goal-oriented editor tasks: it identifies the desired effect or failure mode, then narrows down the likely systems involved. It reads the needed files under references/ on demand, such as inspector.md, physics.md, ui-toolkit.md, animation.md, rendering.md, profiling.md, and build-settings.md, and returns actionable paths. Typical output includes:
- Exact location: menu, window, or component property
- Parameter value: Is Trigger, Raycast Target, Mode, etc.
- Complete plan: related steps are grouped when multiple systems are involved
- Terminology handling: switches between Chinese and English editor terms when appropriate, checking terminology.md as needed

Boundaries

It targets Unity 2022.3 LTS editor workflows, including windows, components, settings, asset management, animation, physics, UI, and build settings. A key constraint is that operational details must come from reference files; if the reference does not provide a clear path or parameter, the skill states that instead of guessing UI locations or inventing parameter names. It is best used as an editor operation guide rather than a replacement for Unity API implementation or project architecture design.