菜单
Use when about to write or install a custom Editor script, add a [MenuItem], build a custom Editor window, or create a one-off Editor helper — to check whether a ready-to-paste template already exists in tooling/<domain>/ before reaching for Unity_CreateScript.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | unity-tooling |
| description | Use when about to write or install a custom Editor script, add a [MenuItem], build a custom Editor window, or create a one-off Editor helper — to check whether a ready-to-paste template already exists in tooling/<domain>/ before reaching for Unity_CreateScript. |
Install-once Editor script templates live under ../../tooling/<domain>/. Check here before writing a new Editor script from scratch.
Reach for tooling/ when the task needs a persistent Editor-side helper rather than a one-shot Unity_RunCommand body. Signals:
[MenuItem("Tools/...")] script via Unity_CreateScript.recipes/<domain>/ carries a "Prerequisite: install Editor script" note pointing at tooling/<domain>/.Do NOT use for one-shot operations — those belong in recipes/<domain>/ and run through Unity_RunCommand.
../../tooling/<domain>/README.md for the domain that matches the task (e.g. tooling/ui/).Unity_CreateScript at the path the tool file specifies.EditorApplication.isCompiling (see UI Authoring Loop Phase 1 in ../ui/SKILL.md).EditorApplication.ExecuteMenuItem.If no tool covers the case, write one — but check first.
| Domain | Folder | Tools |
|---|---|---|
| ui | ../../tooling/ui/ | ui_screenshot_tool |
tooling/ C# block into Unity_RunCommand. These are install-once Editor scripts, not IRunCommand bodies — they will not compile in the RunCommand context. Always install via Unity_CreateScript at the path the tool file specifies.EditorApplication.ExecuteMenuItem immediately after install. Unity needs to recompile the new script before the menu items register. Poll isCompiling first.tooling/ files as compile/run-gated like recipes/. They have no validation gate — install into a scratch project once before trusting at scale.Use when working with a Unity project via MCP — creating or editing scenes, GameObjects, components, prefabs, materials, UI, lighting, navmesh, animations, terrain, C# scripts, or any other Unity Editor task.
Use when users want to run Unity tests or read test results.
Use when users want to enter play mode, select objects, undo/redo, or execute menu commands.
Use when creating, reading, editing, searching, validating, or deleting C# scripts in a Unity project.
Use when users want to create Canvas, Button, Text, Image, or other UI elements.
Use when users want to find unused assets, duplicate files, or clean up the project.