Menu
Use this skill when implementing or verifying USD identifier and name handling.
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-identifiers-and-names |
| description | Use this skill when implementing or verifying USD identifier and name handling. |
| metadata | {"author":"NVIDIA"} |
Use this skill when implementing or verifying USD identifier and name handling.
specification/document_data_model/README.md sections Specs > Names and Metadata Fields > Allowed Namesspecification/file_formats/README.md sections Keywords and IdentifiersPinned tag / commit: v1.0.1
Identifiers are UTF-8 / Unicode code point sequences constrained by the spec's XID start/continue rules. ASCII-only shortcuts may be used only where the spec requires ASCII, such as USDA prim type names.
Property names may contain namespace separators (:). Attribute and
relationship specs sharing a parent may not have the same property name.
This skill owns the reusable identifier scanner capability described by
contracts/capabilities/identifier-scanner.json. Dependent parsers should be
able to ask this skill to consume one identifier, one identifier-continuation
code point, or one namespaced property name from an offset in caller-owned text.
The scanner may return spans, offsets, views, or target-native name values; it
does not need to allocate strings.
The scanner capability owns UTF-8 decoding validity, XID start/continue policy, keywordless identifier policy when requested, and namespaced-name component validity. Callers own their surrounding grammar delimiters and diagnostics.
Defer path parsing to usd-paths.
Defer USDA tokenization details such as comments, strings, numbers, and asset
refs to usda-lexical-format.
Do not silently accept reserved USDA keywords where the grammar requires a keywordless identifier.
goldens/unit/usd-identifiers/identifier-scanner.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.