القائمة
Use this skill when implementing or verifying recursive local sublayer loading from resolved layer resources into a layer-stack namespace source.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | usd-layer-stack-open |
| description | Use this skill when implementing or verifying recursive local sublayer loading from resolved layer resources into a layer-stack namespace source. |
| metadata | {"author":"NVIDIA"} |
Use this skill when implementing or verifying recursive local sublayer loading from resolved layer resources into a layer-stack namespace source.
specification/composition/README.md sublayer and layer-stack inputsspecification/document_data_model/README.md subLayers and subLayerOffsetsPinned tag / commit: v1.0.1
subLayers from the opened root layer and recursively opened local sublayersusd-layer-openLayerStackNamespaceSource from opened layersThis skill owns contracts/handles/layer-stack-open.handle.json and bridges
the single-layer opener with the in-memory layer-stack namespace source.
This is a bounded recursive local sublayer loader. It accepts a resolved root
resource location, opens it with usd-layer-open, reads each opened layer's
authored subLayers field, resolves each local sublayer using the prototype
policy below, opens recursively discovered sublayers with usd-layer-open, and
passes the opened layers to usd-layer-stack-namespace-source.
The output is a target-native result containing either a
LayerStackNamespaceSource or diagnostics. It must not be a canonical JSON
dump, a parser-local USDA tree, or a separate JSON spec store. JSON appears only
in conformance adapters and diagnostic serialization.
This is not full USD asset resolution. It is a bounded local policy for the first actual-sublayer contract:
file URI roots may resolve relative sublayer identifiers against the
containing file URI path of the authoring layerfile URI sublayers may be passed through as resolved
locationsFor this prototype, plain relative asset identifiers such as asset.usda and
anchored relative identifiers such as ./asset.usda are both resolved relative
to the layer that authored the subLayer. This is a local resolver policy, not a
claim of full asset resolution.
Consume usd-layer-open to open the root and every recursive sublayer. Do not read
files directly and do not invoke USDA parsers from this node.
Consume usd-resource-protocol for resolved-location classification and local
resource rules. Do not add ad hoc URI parsing, package splitting, or unsupported
scheme fallback to filesystem paths.
Consume usd-layer-stack-namespace-source to construct the composed namespace
source from opened layers. Do not duplicate child/property composition,
effective specifier rules, or field-strength merging in the loader.
Consume the document-model layer returned by usd-layer-open; do not retain
canonical layer dump JSON as source storage.
Do not perform references, payloads, inherits, specializes, variant composition, relocates, schema fallback evaluation, value resolution, stage population, or instancing.
usd-layer-openusd-layer-openusd-layer-stack-namespace-sourcegoldens/unit/usd-layer-stack-open/layer-stack-open.jsonMap 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.