with one click
ovui
ovui contains 4 collected skills from NVIDIA-Omniverse, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
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 must rebuild Stage-Browser-like, Property-Inspector-like, or Viewport-like UI from primitives without reusing high-level composite widgets. Do not use for ovwidgets composite-widget application work; use the omniverse-ui-widgets skill instead.
Use this skill when the user asks to inspect, screenshot, automate, click, type into, or drive a running ovui/ovwidgets 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 ovui apps launched with PYTHONPATH.
Use this skill for ovui and ovwidgets styling work: palettes, colour / float / URL constants, theme shades, ui.style.default, style dictionaries, selector grammar, widget name variants, style_type_name_override values, naming conventions, style hierarchy, the centralised style module, and styling reviews. This skill is the authoritative target style guide.
Use this skill when a user asks to create or validate a disposable standalone ovui/ovwidgets 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, widget wiring, menu/file-open wiring, and screenshot-first QA expectations. Do not use this skill for raw `omni.ui` atomic widget construction; use the omniverse-ui-apis skill instead.