القائمة
Use this skill when implementing runtime stage-open orchestration for composed USD stages.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | usd-composed-stage-open |
| description | Use this skill when implementing runtime stage-open orchestration for composed USD stages. |
| metadata | {"author":"NVIDIA"} |
Use this skill when implementing runtime stage-open orchestration for composed USD stages.
Normative references:
aousd/specifications-public@v1.0.1:specification/composition/README.mdaousd/specifications-public@v1.0.1:specification/glossaryOwned contracts:
contracts/handles/composed-stage-open.handle.jsoncontracts/spec-coverage/composed-stage-open.coverage.jsonusd-layer-stack-open.payloadInclusion scenario control: open and
supply direct external payload assets for include; omit payload opening and
the payload opinion source for omit.usd-stage-population.usd-composition-arbitrator.usd-stage-population.The generated implementation should load direct local reference dependency
assets. As optional support for the AOUSD population-mask payload flag, for
payloadInclusion=include it should also load direct local payload dependency
assets that can be discovered from opened layer specs. It should then continue
opening reference dependencies discovered in referenced and loaded payload layer
stacks until a bounded fixed point is reached. For payloadInclusion=omit, it
should not open payload assets and should omit the payload opinion source so
payload_loading=absent.
It may still report composition as partial because recursive payload arcs,
variant body arcs, schema fallbacks, full value resolution, and full
instancing/prototypes are not yet covered.
Map unfamiliar or multi-repository codebases before refactoring, integration, or feature work. Use when Codex needs to analyze submodules, ownership boundaries, APIs, duplicate implementations, build/test surfaces, risk areas, and a practical refactor sequence before changing code.
Coordinate multiple AI agents or subagents on software work without duplicating effort or causing conflicts. Use when Codex is explicitly asked to delegate exploration, implementation, review, testing, integration, or parallel analysis across a codebase.
Maintain C ABIs and language bindings as exact, testable contracts. Use when evolving public headers, ctypes/cffi/pybind/Rust/JS bindings, shared libraries, struct layouts, GPU/native APIs, or any cross-language boundary where drift can cause crashes or silent corruption.
Debug rendering, viewer, shader, material, camera, lighting, and GPU integration bugs with reproducible visual evidence. Use when scenes render blank, only appear after camera motion, show incorrect shading, diverge across backends, crash in GUI mode, or need pixel/screenshot verification.
Refactor disjoint or duplicated projects into clear layered architecture with canonical contracts and thin adapters. Use when viewers, renderers, bindings, data libraries, plugins, or services overlap and need maintainable ownership boundaries without losing behavior.
Identify and remove obsolete legacy, fallback, staging, compatibility, duplicate, generated, and reference code before creating clean initial commits or new project history. Use when a repo is being reset, consolidated, or prepared for a cleaner public history.