The standalone distribution of NVIDIA Omniverse's omni.ui UI framework, extracted to run independently outside of Kit. It provides a declarative, Python-first API for building hardware-accelerated desktop interfaces backed by ImGui.
This repository also configures its own agents. See what ovui tells them →
Skill Claude CodeCodex
Use when creating, modifying, inspecting, or reasoning about ovui UI from low-level atomic ovui widgets, including layout, Pixel/Percent/Fraction sizing, model-view widgets, TreeView/stage hierarchy trees, inputs, menus, windows, docking, viewport-like ovrtx panels, styling, or strict UI validation. Use when an agent…
Skill Claude CodeCodex
Use this skill when the user asks to inspect, screenshot, automate, click, type into, or drive a running ovui/ovui-widgets application through the ovui-inspect FastAPI inspector. The skill provides an importable ovuiinspect module, an ovui-inspect CLI, and a screenshot-first mouse/keyboard workflow for controlling…
Skill Claude CodeCodex
Use this skill for ovui and ovui-widgets styling work: palettes, colour / float / URL constants, theme shades, ui.style.default, style dictionaries, selector grammar, widget name variants, styletypenameoverride values, naming conventions, style hierarchy, the centralised style module, and styling reviews. This skill…
Skill Claude CodeCodex
Install and run the packaged ovui USD Viewer with ovrtx and either OpenUSD, ovstage, or both data adapters. Use when creating a clean virtual environment from published wheels, selecting the adapter configuration, or launching ovuiwidgets.app against a USD file.
Skill Claude CodeCodex
Use this skill when a user asks to create or validate a disposable standalone ovui/ovui-widgets application from the existing widget set. The application source should live outside the repo unless the user explicitly asks to productize it. The skill gives exact imports, runtime environment, ovrtx proof requirements…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: