USD Editor
Quick Start
Use this skill for minimal, text-level USD or USDA edits and command-line USD
inspection, conversion, packaging, rendering, and validation. Keep the change
small and preserve existing composition unless the task explicitly says
otherwise.
When authored Reality Composer Pro or USD content owns the scene, geometry,
transform, animation, or material, keep that authored surface as the source of
truth. Use Swift and RealityKit to load or adjust runtime state; do not recreate
authored USD content in Swift unless the request is explicitly procedural.
If Swift code needs to open, edit, observe, or export stages in-process with
USDStage, USDPrim, or USDLayer, switch to $usdkit-runtime-developer.
If the change is material- or shader-specific for RealityKit, prefer
shadergraph-editor.
Load References When
| Reference |
When to Use |
usd-syntax |
When you need a refresher on .usda syntax, values, and path formats. |
prims-properties |
When adding or editing prims, attributes, or relationships. |
composition-variants |
When touching sublayers, references, payloads, or variant sets. |
transforms-units |
When editing transforms, xformOps, or stage units and up-axis metadata. |
time-samples |
When modifying animated or time-sampled properties. |
command-line-tools |
When you need a quick reference for common USD command-line tools. |
usdcat |
When converting, flattening, or inspecting USD files. |
usdchecker |
When validating USD or USDZ assets, including RealityKit-focused checks. |
usdrecord |
When rendering images from USD files. |
usdtree |
When inspecting the prim hierarchy of a USD file. |
usdzip |
When creating or inspecting USDZ packages. |
usdedit |
When you need the official text-editing workflow for a USD-readable file. |
visionos-runtime-loading.md |
When the question is how authored USD or USDZ actually loads and behaves in a visionOS app. |
apple-runtime-boundaries.md |
When deciding whether to edit authored USD / Reality Composer Pro content, load it through RealityKit, or validate it for Apple platforms. |
Workflow
- Identify the owner: authored USD / Reality Composer Pro asset, package
resource, or runtime-only Swift-generated content.
- Inspect the stage with
usdtree, usdcat --loadOnly, or usdcat --flatten
before editing, depending on the risk.
- Locate the exact prim path and layer that owns the opinion.
- Choose
over, def, or a list edit deliberately.
- Apply the minimum change needed.
- Re-check paths, transforms, or composition edges that were touched.
- Run the narrowest validation tool that matches the change, then run
usdchecker --arkit for shipping visionOS USDZ assets.
Guardrails
- Do not replace a prim with
def when over is the correct edit.
- Avoid composition-arc changes unless they are explicitly requested.
- If a RealityKit app loads the asset with
Entity(named:in:),
Entity(contentsOf:withName:), or a generated Reality Composer Pro content
bundle, prefer fixing the authored asset and validating the bundle/package
over building a parallel Swift scene graph.
- Do not hand-edit a
.usdz package in place; inspect or unpack it, edit the
source layer, rebuild the package, and validate the result.
- Validate final Apple-platform USDZ output with
usdchecker --arkit --strict,
not just a source-layer parse check.
- Preserve existing formatting and comments when possible.
Output Expectations
Provide:
- the prim or path edited
- which reference files were used
- the exact class of USD change made
- the validation step used
- routing to
$usdkit-runtime-developer, shadergraph-editor, or runtime
testing if needed
1---2name: usd-editor3description: Guide for modifying USD ASCII (.usda) files and command-line USD workflows, including prims, properties, composition arcs, variants, transforms, usdcat, usdchecker, usdrecord, usdtree, usdzip, and usdedit. Use when editing or reviewing .usda files by hand, validating USD/USDZ assets, or working in an asset pipeline outside runtime Swift USDKit.4---56# USD Editor78## Quick Start910Use this skill for minimal, text-level USD or USDA edits and command-line USD11inspection, conversion, packaging, rendering, and validation. Keep the change12small and preserve existing composition unless the task explicitly says13otherwise.1415When authored Reality Composer Pro or USD content owns the scene, geometry,16transform, animation, or material, keep that authored surface as the source of17truth. Use Swift and RealityKit to load or adjust runtime state; do not recreate18authored USD content in Swift unless the request is explicitly procedural.1920If Swift code needs to open, edit, observe, or export stages in-process with21`USDStage`, `USDPrim`, or `USDLayer`, switch to `$usdkit-runtime-developer`.2223If the change is material- or shader-specific for RealityKit, prefer24`shadergraph-editor`.2526## Load References When2728| Reference | When to Use |29|-----------|-------------|30| [`usd-syntax`](references/usd-syntax.md) | When you need a refresher on .usda syntax, values, and path formats. |31| [`prims-properties`](references/prims-properties.md) | When adding or editing prims, attributes, or relationships. |32| [`composition-variants`](references/composition-variants.md) | When touching sublayers, references, payloads, or variant sets. |33| [`transforms-units`](references/transforms-units.md) | When editing transforms, xformOps, or stage units and up-axis metadata. |34| [`time-samples`](references/time-samples.md) | When modifying animated or time-sampled properties. |35| [`command-line-tools`](references/command-line-tools.md) | When you need a quick reference for common USD command-line tools. |36| [`usdcat`](references/usdcat.md) | When converting, flattening, or inspecting USD files. |37| [`usdchecker`](references/usdchecker.md) | When validating USD or USDZ assets, including RealityKit-focused checks. |38| [`usdrecord`](references/usdrecord.md) | When rendering images from USD files. |39| [`usdtree`](references/usdtree.md) | When inspecting the prim hierarchy of a USD file. |40| [`usdzip`](references/usdzip.md) | When creating or inspecting USDZ packages. |41| [`usdedit`](references/usdedit.md) | When you need the official text-editing workflow for a USD-readable file. |42| [`visionos-runtime-loading.md`](references/visionos-runtime-loading.md) | When the question is how authored USD or USDZ actually loads and behaves in a visionOS app. |43| [`apple-runtime-boundaries.md`](references/apple-runtime-boundaries.md) | When deciding whether to edit authored USD / Reality Composer Pro content, load it through RealityKit, or validate it for Apple platforms. |4445## Workflow46471. Identify the owner: authored USD / Reality Composer Pro asset, package48 resource, or runtime-only Swift-generated content.492. Inspect the stage with `usdtree`, `usdcat --loadOnly`, or `usdcat --flatten`50 before editing, depending on the risk.513. Locate the exact prim path and layer that owns the opinion.524. Choose `over`, `def`, or a list edit deliberately.535. Apply the minimum change needed.546. Re-check paths, transforms, or composition edges that were touched.557. Run the narrowest validation tool that matches the change, then run56 `usdchecker --arkit` for shipping visionOS USDZ assets.5758## Guardrails5960- Do not replace a prim with `def` when `over` is the correct edit.61- Avoid composition-arc changes unless they are explicitly requested.62- If a RealityKit app loads the asset with `Entity(named:in:)`,63 `Entity(contentsOf:withName:)`, or a generated Reality Composer Pro content64 bundle, prefer fixing the authored asset and validating the bundle/package65 over building a parallel Swift scene graph.66- Do not hand-edit a `.usdz` package in place; inspect or unpack it, edit the67 source layer, rebuild the package, and validate the result.68- Validate final Apple-platform USDZ output with `usdchecker --arkit --strict`,69 not just a source-layer parse check.70- Preserve existing formatting and comments when possible.7172## Output Expectations7374Provide:75- the prim or path edited76- which reference files were used77- the exact class of USD change made78- the validation step used79- routing to `$usdkit-runtime-developer`, `shadergraph-editor`, or runtime80 testing if needed
tomkrikorian