Menu
Use this skill when implementing authored list operation values as they appear in a single layer.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | usd-listops-authored |
| description | Use this skill when implementing authored list operation values as they appear in a single layer. |
| metadata | {"author":"NVIDIA"} |
Use this skill when implementing authored list operation values as they appear in a single layer.
specification/foundational_data_types/README.md section List Operationsspecification/file_formats/README.md section A General Note on ListopsPinned tag / commit: v1.0.1
None as empty listOp outside attribute value assignmentThis skill owns contracts/handles/listops-authored.handle.json and stores
authored list operations. It does not combine list operations across layer
opinions.
Implementations should keep listOps in native authored storage with one item list per authored subfield: explicit, prepend, append, and delete. Tagged JSON is only the adapter/dump representation and should be materialized on demand.
The core listOp value model stores typed items, not parsed strings. The native item representation is:
usd-pathsusd-tokensCanonical dump shape:
{
"type": "listop<ObjectPath>",
"value": {
"explicit": ["/A"],
"prepend": [],
"append": [],
"delete": []
}
}
Defer item equality for paths to usd-paths.
Defer token identity to usd-tokens.
Defer scalar eligibility and integer width/range rules to
usd-foundational-values.
Do not implement cross-layer listOp composition or value resolution.
Do not retain tagged JSON as the backing listOp representation.
Do not parse USDA text syntax in this capability. USDA syntax belongs to the USDA parser skills.
Do not make JSON parsing or JSON-number/string coercion part of the core listOp model. JSON coercion belongs only in the handle adapter.
Do not store ObjectPath, token, or numeric listOp items as durable strings.
Strings are the native storage type only for listOp<string>.
Do not store listOp<Reference> or listOp<Payload> items as dictionaries,
bare asset strings, or bare path strings. Those shapes are parser input or
dump-adapter output only; the domain item is a typed arc record.
usd-pathsgoldens/unit/usd-listops-authored/listops-authored.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.