메뉴
Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | omniverse-realtime-viewer |
| description | Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents. |
| version | 0.1.0 |
| license | Apache-2.0 |
| tools | ["Read","Shell","Write"] |
| compatibility | Orchestrator skill. Downstream focused references may require NVIDIA GPUs, ovrtx, ovstream, ovui, OpenUSD, Python, Node/React, Tauri, Electron, C++, or cloud GPU deployment access depending on the selected viewer path. |
| metadata | {"author":"NVIDIA Omniverse","tags":["omniverse","usd","viewer","workflow"],"domain":"ai-ml","languages":["python","typescript","cpp"]} |
This is the top-level entry point for the Omniverse Realtime Viewer skill package. It is self-contained: all required routing, conventions, and validation guidance live in the selected references.
Use the focused reference documents as implementation recipes. This file chooses the right recipes and preserves the architectural rules that must hold across all generated viewer apps.
Start by classifying the requested viewer, then read only the references needed
for that delivery path and feature set. Implement the render path first, layer
interaction and UI behavior on top of it, and finish by capturing validation
evidence from references/validation.md.
references/routing.md to choose the delivery path and focused references.references/conventions.md before implementing camera, input,
selection, viewport, streaming protocol, scene loading, or environment
behavior.references/usd-viewer-app/README.md.references/streaming-vs-local/README.md.references/viewer-ux-workflow/README.md and then the focused viewer UI references.
This applies to React/WebRTC, Tauri, Electron, ovui, ovwidgets, and Dear
ImGui apps; "frontend" means user-facing UI, not only browser UI.references/viewer-input-routing/README.md before
references/camera-controls/README.md, references/native-picking-selection/README.md, or references/object-selection/README.md.references/validation.md to capture review evidence before handoff.ovrtx for all USD and 3D rendering.ovstream WebRTC video stream plus UI. The browser
does not render USD geometry.ovrtx path and document the runtime requirement. Do not add a
browser-renderer fallback.renderer.step(), stage mutation, native picking,
selection writes, and live attribute writes.references/dependencies/README.md and deployment choices in
references/cloud-deployment/README.md; do not duplicate package locations or deployment setup.references/usd-viewer-app/README.md, references/streaming-viewer-recipe/README.md,
references/ovui-local-viewer-recipe/README.md, references/streaming-vs-local/README.md, references/electron-shm-viewer/README.md,
references/ovwidgets-editor-shell/README.md.references/ovrtx-rendering/README.md, references/stage-loading/README.md, references/stage-management/README.md,
references/render-settings/README.md, references/aov-switching/README.md, references/stage-hierarchy/README.md, references/stage-queries/README.md,
references/stage-attribute-reads/README.md, references/prim-transform-safety/README.md, references/usd-sample-data/README.md.references/streaming-server/README.md, references/streaming-client/README.md,
references/streaming-messages/README.md, references/streaming-lifecycle/README.md, references/local-viewer/README.md,
references/tauri-local-viewer/README.md, references/cpp-native-viewer/README.md, references/headless-shm-cli/README.md,
references/viewer-backend-interface/README.md, references/webgl-shm-transport/README.md.references/viewer-ux-workflow/README.md, references/viewer-layout-patterns/README.md,
references/viewer-control-patterns/README.md, references/viewer-data-view-patterns/README.md,
references/viewer-feedback-status/README.md.references/viewer-input-routing/README.md, references/camera-controls/README.md,
references/object-selection/README.md, references/native-picking-selection/README.md, references/selection-feedback/README.md,
references/selection-animation/README.md, references/transform-manipulator/README.md, references/gl-viewport-overlay/README.md,
references/ovui-library/README.md, references/prim-pick-effects/README.md, references/prim-info-display/README.md,
references/viewport-overlays/README.md.references/dependencies/README.md, references/windows-native-setup/README.md, references/cloud-assets/README.md,
references/cloud-deployment/README.md, references/troubleshooting/README.md.references/conventions.md.references/validation.md.Use this skill when implementing a Figma design as code (design → code) — the read-FROM-Figma direction. Triggers: 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'code this up from Figma', 'design to code', or a figma.com design URL provided alongside a codebase. Encodes the workflow for reading a node out of Figma with get_design_context and adapting its reference output to the target project — reusing existing components, tokens, and conventions, and honoring Code Connect mappings, component docs, design annotations, and design tokens by priority. Complements figma-code-connect (component mapping) and figma-generate-design / figma-use (the reverse, code → design direction).
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide or scoped-path Codex Security scan. Run repeated independent discovery passes over one resolved scope with worker-specific threat models, semantically merge candidates, synthesize one canonical validation threat model, then run validation, attack-path analysis, canonical JSON completion, and generated reporting once. Do not use for PRs, commits, branch diffs, or working-tree diffs.
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic improvements, alternatives beyond per-finding patches, before-and-after security architecture views, engineering tradeoff analysis, or an implementation-ready plan for a selected hardening option. Also use automatically after a Codex Security scan with reportable findings when the top-level scan workflow requests final-report hardening guidance.