RealityKit visionOS Developer

Quick Start

1. Classify the request as core scene setup, rendering/materials, animation/physics, audio, custom ECS, USD authoring, Spatial Preview, SwiftUI UI, ARKit provider work, or build/debug plumbing.
2. Stay in this skill for RealityView setup, entity loading, component selection, input, attachments, anchoring, portals, synchronization, and the local USDStageComponent bridge.
3. Switch to the focused RealityKit skill when the task is primarily visual, animated, physical, audio, or custom ECS behavior.
4. Load only the narrow reference files needed for the task.
5. Keep all scene mutation inside documented RealityKit entry points: RealityView content/update closures, event handlers, or registered systems.

RealityKit Routing