domains / families / software-engineering / ui

ui

combined

Create and lay out Unity UGUI screens Routes Unity UI requests to the right framework skill (UI Toolkit, uGUI, or IMGUI) and answers UI comparison questions. Use for menus, HUDs, panels, or editor UI when the request doesn't name a framework. Consult before writing any UI code.

When to use

• Use this skill when you need to work with opinionated, evolving constraints to guide agents when building interfaces.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

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.