tomkrikorian/visionosagents/realitykit-visionos-developer

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.

1. Stay in this skill for RealityView setup, entity loading, component

selection, input, attachments, anchoring, portals, synchronization, and the local USDStageComponent bridge.

1. Switch to the focused RealityKit skill when the task is primarily visual,

animated, physical, audio, or custom ECS behavior.

1. Load only the narrow reference files needed for the task.
2. Keep all scene mutation inside documented RealityKit entry points:

RealityView content/update closures, event handlers, or registered systems.

RealityKit Routing

Load References When

Guardrails

• Use RealityView; ARView is not available on visionOS.
• Load assets asynchronously and avoid blocking the main actor.
• Keep SwiftUI body code declarative; mutate RealityKit content through

RealityView, events, or systems.

• Prefer documented components before custom ECS.
• Register custom components and systems once during app startup before scenes

or assets that depend on them load.

• Prefer ManipulationComponent.configureEntity(...) when built-in direct

manipulation fits the need.

• Use SpatialPreview only from macOS 27 sender apps; Vision Pro uses the

built-in system viewer and has no visionOS SpatialPreview module.

Output Expectations

Provide:

• the RealityKit task category
• which focused skill or references were used
• the component, attachment, entity-loading, or system path chosen
• the main constraint or pitfall
• routing back to SwiftUI, ARKit, USD, Spatial Preview, or build-debug if needed