# Choose the Right Unity UI Framework

Unity projects can mix UI frameworks, making implementation choices unclear. This skill explains framework differences and routes requests using existing project patterns.

## Install

```bash
npx skillstore add unity-technologies/ui
```

## Metadata

- Status: approved
- Slug: unity-technologies-ui
- Skillstore revision: r1
- Version status: missing
- Tree hash: 35f3b465f329ad3ebc5a92dad573801d66bb7d88b607bdab25a4482b262fdaf4
- Author: unity-technologies
- GitHub username: unity-technologies
- License: MIT
- Repository: https://github.com/unity-technologies/skills/tree/9d282100540601cfddc4bbd69f36a239d7a6f55c/skills/ui
- Ref: e406bf64b5db6e514879399e87b346fa7ff7c2fb
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/unity-technologies-ui
- Manifest: https://skillstore.pages.dev/api/skills/unity-technologies-ui/manifest

## Capabilities

- Routes explicit framework names, file extensions, and Unity UI component references to the appropriate specialized skill.
- Guides project inspection using UXML, USS, UIDocument, Canvas, RectTransform, and editor method clues.
- Answers conceptual questions about Unity UI architecture and framework selection without routing.
- Distinguishes runtime and editor requests when a project contains multiple UI systems.
- Applies default framework choices when project evidence and user preferences are absent.
- Identifies unsupported automated Figma imports and offers description or screenshot alternatives.

## Use Cases

- Choose a Framework for a New Game Menu: Identify preferences and project constraints before routing a new runtime menu request to the appropriate framework skill.
- Route a Custom Inspector Request: Check existing editor UI patterns and choose UI Toolkit or IMGUI for an inspector or editor window request.
- Compare Unity UI Options: Get a conceptual comparison of UI Toolkit, uGUI, and IMGUI without changing project files.

## Prompt Templates

### Compare Frameworks

```
Explain the main differences between UI Toolkit, uGUI, and IMGUI for Unity interfaces. Do not change any files.
```

### Select a Runtime UI Framework

```
I need a settings menu for a new Unity game. Check existing UI patterns and ask about missing preferences before choosing a framework.
```

### Route an Existing Layout Edit

```
My inventory screen uses UXML and USS. Route a spacing adjustment to the appropriate specialized skill without adding interaction scripts.
```

### Resolve a Mixed Project

```
Inspect runtime and editor UI patterns in this mixed Unity project. Recommend separate routes for a HUD edit and a new editor window.
```

## Limitations

- Implementation depends on separate ui-uitk, ui-ugui, and ui-imgui skills, which are not included in this package.
- Automated Figma design import is unavailable through this skill.
- Project-specific framework detection requires access to relevant Unity project files.
- Visual UI requests do not include interaction scripts unless the user explicitly requests them.

## Best Practices

- Provide framework names, relevant file types, and whether the request targets runtime UI or editor tools.
- Check existing project patterns before accepting a default framework recommendation.
- State whether you need explanation, a targeted visual edit, or generation, and explicitly request any interaction scripts.

## Anti Patterns

- Treating this routing skill as a replacement for the specialized implementation skills.
- Using one framework choice for every runtime and editor request in a mixed project.
- Expecting automatic Figma import or interaction scripts from a visual layout request.

## Security Audit

- Audited at: 2026-10-10T14:09:56.88\+00:00
- Summary: All 24 static findings are false positives: 22 match Markdown code formatting, and two match ordinary UI descriptions. No evidence found of command execution, system reconnaissance, data exfiltration, or prompt injection in the reviewed SKILL.md. Referenced specialized skills are not included, so their behavior is outside this audit.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0