domains / software-engineering / unity-ui-routing / ui
The three copies describe three different procedures for the same 'ui' skill name. The Unity-Technologies copy is a router that decides between UI Toolkit, uGUI, and IMGUI. The Besty0728 copy is a concrete UGUI execution module with specific API calls and hallucination guards. The sickn33 copy is a generic, low-content wrapper for a web UI design skill. Because they overlap in the broad 'UI' domain but contain material, non-reproducible steps and constraints specific to each (routing logic vs. API execution vs. design review), crowning one would hide the others' real functionality.
| Repository | Path |
|---|---|
| Unity-Technologies/skills | skills/ui/SKILL.md |
| Besty0728/Unity-Skills | SkillsForUnity/unity-skills~/skills/ui/SKILL.md |
| sickn33/agentic-awesome-skills | plugins/agentic-awesome-skills-claude/skills/ui-skills/SKILL.md |
| Role | Repository | Path |
|---|---|---|
| peer | Unity-Technologies/skills | skills/ui/SKILL.md |
| peer | Besty0728/Unity-Skills | SkillsForUnity/unity-skills~/skills/ui/SKILL.md |
| peer | sickn33/agentic-awesome-skills | plugins/agentic-awesome-skills-claude/skills/ui-skills/SKILL.md |
| adapter | sickn33/agentic-awesome-skills | plugins/agentic-awesome-skills/skills/ui-skills/SKILL.md |
| adapter | sickn33/agentic-awesome-skills | skills/ui-skills/SKILL.md |
--- name: ui description: Handles Unity UI requests by routing to the correct framework (UI Toolkit, uGUI, IMGUI) or providing design guidance for web interfaces. --- ## 1. Determine Context - If the request is for a **Unity project**, proceed to Step 2. - If the request is for a **web interface** or general design review, use the design constraints from the `ui-skills` source (ibelick/ui-skills) to identify high-impact design problems. ## 2. Unity Framework Routing - **UI Toolkit**: Route to `ui-uitk` if the user mentions `.uxml`, `.uss`, `UIDocument`, or `CreateGUI`. - **uGUI**: Route to `ui-ugui` if the user mentions `Canvas`, `RectTransform`, or `.prefab` UI. If no framework is specified for a new runtime UI, default to uGUI. - **IMGUI**: Route to `ui-imgui` only if the project exclusively uses `OnGUI`/`OnInspectorGUI` or the user explicitly requests it. ## 3. UGUI Execution (if routed to uGUI) - **Batch-first**: Use `ui_create_batch` for 2+ elements. - **Avoid Hallucinations**: Do not use `ui_add_canvas` (use `ui_create_canvas`), `ui_create_label` (use `ui_create_text`), or `ui_create_checkbox` (use `ui_create_toggle`). - **Workflow**: Create elements first, then use `ui_set_rect` or `ui_set_anchor` for placement. Use `ui_layout_children` for responsive layouts. ## 4. Common Guidelines - **Scope Discipline**: Do only what is requested. Do not add scripts unless explicitly asked. - **Project Patterns**: Search existing files to match naming conventions and file organization before applying defaults. - **Figma**: If a Figma URL is provided for Unity, inform the user that automated import is not available and ask for a description or screenshot.