shadergraph-editor
ShaderGraph Editor
Quick Start
Default to Reality Composer Pro. Use raw USD or MaterialX inspection only when debugging exports or interoperability.
- Decide whether the task is node selection, runtime parameter control, export debugging, or sample selection.
- Load only the matching reference files.
- Route text-level USD structure edits to
usd-editor.
Load References When
| Reference | When to Use |
|---|---|
references/shadergraph-node-reference.md |
When choosing RealityKit Shader Graph nodes by category. |
references/runtime-api.md |
When loading ShaderGraphMaterial, working with promoted inputs, or updating parameters at runtime. |
references/export-debug.md |
When inspecting exported USD or MaterialX, or when a graph fails to load or render as expected. |
references/samples.md |
When selecting the closest repo sample before authoring a new effect from scratch. |
Workflow
- Start from the closest existing sample when possible.
- Author or refine the graph in Reality Composer Pro.
- Promote the inputs that need runtime control.
- Load and update the material through the runtime API.
- Inspect exports only when the normal authoring path stops explaining the failure.
When To Switch Skills
- Switch to
usd-editorwhen the task is really about prim paths, composition, or text-level USD authoring. - Switch to
realitykit-visionos-developerwhen the blocker is entity setup, material application, or scene integration rather than graph authoring.
Guardrails
- Treat Reality Composer Pro as the default authoring surface.
- Do not treat exported
info:idstrings or raw graph layout as stable public API unless Apple documents them directly.
Output Expectations
Provide:
- the selected effect or sample starting point
- which references were used
- how the material is authored or loaded
- whether the issue is a graph problem, runtime problem, or export problem
- explicit routing to
usd-editoror RealityKit work if needed
More from tomkrikorian/visionosagents
realitykit-visionos-developer
Build, debug, and optimize RealityKit scenes for visionOS 26, including entity/component setup, rendering, animation, physics, audio, input, attachments, and custom systems. Use when implementing RealityKit features or troubleshooting ECS behavior on visionOS.
62arkit-visionos-developer
Build and debug ARKit features for visionOS 26, including ARKitSession setup, authorization, data providers (world tracking, plane detection, scene reconstruction, hand tracking), anchor processing, and RealityKit integration. Use when implementing ARKit workflows on visionOS or troubleshooting provider-specific space, privacy, and lifecycle behavior.
55spatial-swiftui-developer
Design and implement visionOS 26 SwiftUI scenes that integrate RealityKit content. Use when building spatial UI with RealityView, Model3D, attachments, volumetric windows, ImmersiveSpace, or spatial gestures, or when choosing SwiftUI vs RealityKit APIs for 3D presentation.
47coding-standards-enforcer
Enforce repository coding standards for Swift 6.2 strict concurrency, actor isolation, @Observable models, SWIFT_APPROACHABLE_CONCURRENCY, @concurrent functions, and modern Swift APIs across visionOS app code. Use when reviewing, writing, or migrating Swift code in this plugin's scope.
44usd-editor
Guide for modifying USD ASCII (.usda) files, including prims, properties, composition arcs, variants, and transforms. Use when editing or reviewing .usda files by hand.
32shareplay-developer
Build, integrate, and troubleshoot SharePlay GroupActivities features for visionOS 26, including GroupActivity definitions, activation flows, GroupSession lifecycle, messaging and journals, ShareLink and SharePlay UI surfaces, and spatial coordination.
23