메뉴
Build Unity UI with UI Toolkit — UXML structure, USS styling, data binding, and the runtime vs Editor UI split. Use when creating or editing .uxml or .uss files, building runtime HUDs/menus or custom Editor windows/inspectors with UI Toolkit (not uGUI).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Protect Unity project integrity when touching assets — keep .meta/GUID pairing intact, never hand-edit scene/prefab YAML or binary assets, route hierarchy/prefab changes through the Editor, and keep .gitignore/LFS/merge config correct. Use before moving, renaming, or deleting Unity assets, or when editing .meta, .unity, .prefab, or .asset files.
Run headless Unity builds and CI — batchmode player builds, Addressables content builds, and test/build pipelines (GameCI). Invoke deliberately with /unity-build; this never auto-runs because builds are long and side-effecting.
Write idiomatic, performance-safe Unity 6 C# — MonoBehaviour lifecycle, ScriptableObject + event-channel architecture, serialization, the Input System, and assembly definitions. Use when writing or editing Unity C# scripts (.cs), adding gameplay systems, components, or ScriptableObjects, or wiring data and events in a Unity project.
Drive the live Unity Editor as a feedback loop — recompile after edits, read the console for compile errors and runtime exceptions, capture the Game/Scene view to verify visually, and debug runtime issues. Use after editing Unity scripts, when the game misbehaves or throws, or when you need to see what the Editor is actually rendering.
Diagnose and fix Unity performance problems with a profiler-guided workflow — eliminate GC allocations and per-frame spikes, pool objects, batch work, and measure before and after. Use when a Unity game is slow, stuttering, dropping frames, or showing GC spikes, or when asked to optimize Unity runtime performance.
Write and run Unity Test Framework tests — EditMode (fast, logic) and PlayMode (scene/lifecycle) — via headless batchmode, parse the NUnit XML results, and pair them with visual capture so "tests pass" actually means "the game works". Use when adding or running Unity tests, setting up test assemblies, or verifying gameplay behavior.
| name | unity-ui-toolkit |
| description | Build Unity UI with UI Toolkit — UXML structure, USS styling, data binding, and the runtime vs Editor UI split. Use when creating or editing .uxml or .uss files, building runtime HUDs/menus or custom Editor windows/inspectors with UI Toolkit (not uGUI). |
| when_to_use | Editing .uxml or .uss; building a UI Toolkit HUD, menu, custom Editor window, or custom inspector; questions about UXML/USS, UQuery, UIDocument, or data binding. (For legacy Canvas/uGUI UI, this skill does not apply.) |
| paths | **/*.uxml,**/*.uss |
UI Toolkit is the modern, retained-mode UI system: structure in UXML (XML), styling in USS (CSS-like), queried and driven from C#. It powers both runtime UI and Editor tooling. First confirm the project actually uses UI Toolkit and not legacy uGUI Canvas — they don't mix well; follow whichever the project established.
VisualElement, Label, Button, ListView, etc.). Keep it structural; no inline styling beyond layout intent.flex-direction, flex-grow, align-items), colors, fonts. Selectors by type, .class, and #name. Reuse classes; avoid styling by name where a class fits.public sealed class HUD : MonoBehaviour
{
[SerializeField] private UIDocument document; // runtime UI entry point
private Label _score;
private void OnEnable()
{
var root = document.rootVisualElement;
_score = root.Q<Label>("score-label"); // UQuery by name
root.Q<Button>("pause").clicked += OnPause;
}
public void SetScore(int value) => _score.text = value.ToString();
}
root.Q<Label>("score-label") with a name that doesn't exist in the UXML compiles fine and returns null silently — the failure surfaces later as a NullReferenceException far from the typo, or as UI that just doesn't update. The compiler will not save you. So:
Q<T>("name") or .Q(className: "x"), grep the actual .uxml for that name= / class= attribute. Copy the string from the file — don't retype it, and never guess it from what the element "would be called.".uxml/.uss files for the class.Assert.IsNotNull or an explicit log) so a broken binding fails loudly at OnEnable, not silently at first use.Q<Label>("x") returns null if x exists but is a Button. Verify the element's tag in the UXML, not just its name.UIDocument component referencing a Panel Settings asset and your UXML. Lives in the scene.CreateGUI() / CreateInspectorGUI() and lives under an Editor/ folder/asmdef — never shipped at runtime (see unity-csharp Editor-code rule).Same UXML/USS authoring model; different entry point and assembly. Keep them separate.
Unity 6 supports runtime data binding (SerializedObject bindings in the Editor; binding paths and INotifyBindablePropertyChanged at runtime). Prefer binding over manually pushing values every frame. For lists, use ListView/MultiColumnListView with makeItem/bindItem and virtualization rather than instantiating elements per row.
OnEnable; don't Q<>() every frame (it walks the tree — same spirit as the GetComponent rule).display: none / DisplayStyle rather than rebuilding the tree..uxml/.uss are text and safe to edit, but their .meta files still pair (and any referencing .asset/scene wiring goes through the Editor).