skills.rest
NVIDIA-Omniverse
NVIDIA-OmniverseOFFICIAL
Explore all skills by this author →
Website𝕏@nvidiaomniverseGitHub

omniverse-ui-styling

Consolidate OVUI/OVWidgets styling into a centralized style system with design tokens and overrides.

51|5|Updated May 18, 2026
Search Tags:#styling#constants#palette#selectors#ovui#ui.style.default#style-hierarchy
One-click install
npx skills add https://github.com/NVIDIA-Omniverse/ovui --skill omniverse-ui-styling
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omniverse-ui-styling
Source: https://github.com/NVIDIA-Omniverse/ovui/tree/main/skills/omniverse-ui-styling
Command: npx skills add https://github.com/NVIDIA-Omniverse/ovui --skill omniverse-ui-styling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates OVUI/OVWidgets styling into a single, maintainable style system that ensures visual consistency.

Core Features & Use Cases

  • Centralised stores (palette, constants, urls), a GLOBAL_STYLES dictionary, and a standard workflow for per-surface overrides.
  • Domain-scoped style types (style_type_name_override) and named variants (name selectors) to support scalable, consistent styling across multiple surfaces.
  • Theme shading integration and a centralized startup flow to apply and propagate style changes automatically.

Quick Start

Create a centralised style module following the reference guides to establish a consistent OVUI look across all widgets.

Frequently Asked Questions about omniverse-ui-styling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent OVUI styling across multiple widget surfaces?▼

Consistent OVUI styling is enforced by consolidating design tokens, palette constants, and a GLOBAL_STYLES dictionary into a centralized style system. This ensures visual consistency by applying strict naming and selector rules across all widget surfaces automatically.

What is the best way to manage OVWidgets style overrides without breaking the global theme?▼

Managing OVWidgets style overrides without breaking the global theme requires domain-scoped style types and named variant selectors. This scalable workflow allows per-surface visual adjustments while maintaining the centralized GLOBAL_STYLES dictionary and automatic theme shading integration.

How do OVUI design tokens and style dictionaries propagate changes to all surfaces?▼

Design tokens and style dictionaries propagate changes through a centralized startup flow that applies and propagates style updates automatically. This ensures centralized stores for palette and constants push consistent visual updates across all active surfaces.

Can I apply custom palette colors and theme shading to specific OVUI surfaces?▼

Custom palette colors and theme shading can be applied to specific OVUI surfaces using per-surface overrides. The system supports domain-scoped style types and named selectors, while the centralized startup flow handles theme shading integration automatically.

Why do my OVUI widgets display inconsistent visuals instead of the expected global styles?▼

Inconsistent OVUI widget visuals occur when bypassing the centralized style system and its GLOBAL_STYLES dictionary. Enforcing strict naming and selector rules alongside centralized palette stores ensures all widgets retrieve styling from a single maintainable source.

Related Skills

Explore More Software Engineering Skills→
chetan2921chetan2921

riverpod-eager-initialization

Configure Riverpod providers to initialize at app startup in a root Consumer widget.

Community
Basic
stephanjstephanj
9

design-system-starter

Create design systems with design tokens, atomic components, and WCAG 2.1 AA compliance.

Community
Advanced
wot-uiwot-ui
284

generate-theme

Generate a single-file SCSS theme for Wot UI with fixed color tokens.

Official
Intermediate
NymfariousNymfarious
1

theming-with-tokens

Define centralized CSS token themes with per-canvas overrides for host widgets.

Community
Advanced