Covers the three scene types available — WindowGroup (2D windows in space), Volume (3D bounded content), and ImmersiveSpace (full immersive experience) — with references on windows/volumes/spaces, RealityView/3D content, and ornament-based 2D UI attachments.
Best practices: start with familiar 2D windows before adding depth, introduce volumes gradually for 3D content, use ornaments to attach 2D UI to 3D scenes, respect the user's physical space rather than overwhelming it, design for natural hand tracking, and avoid rapid movements that cause eye discomfort.
visionOS PlatformvisionOS-specific development for Apple Vision Pro spatial computing.
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Analyze existing visionOS patterns
- fuse-ai-pilot:research-expert - Verify latest visionOS 27 docs via Context7/Exa
- mcp__apple-docs__search_apple_docs - Check spatial computing patterns
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
When to Use
- Building Vision Pro applications
- Creating 3D spatial experiences
- Mixed reality features
- Immersive environments
- Hand and eye tracking
Why visionOS Skill
| Feature | Benefit |
|---|---|
| Spatial computing | 3D interaction |
| RealityKit | 3D content rendering |
| Immersive spaces | Full environment |
| Volumes | 3D bounded content |
Scene Types
| Scene | Description |
|---|---|
| WindowGroup | 2D windows in space |
| Volume | 3D bounded content |
| ImmersiveSpace | Full immersive experience |
Reference Guide
| Need | Reference |
|---|---|
| Windows, volumes, spaces | spatial-computing.md |
| RealityView, 3D content | realitykit.md |
| Attachments, UI ornaments | ornaments.md |
Best Practices
- Start with windows - Familiar 2D first
- Add depth gradually - Volumes for 3D
- Use ornaments - Attach 2D UI to 3D
- Respect space - Don't overwhelm user
- Hand tracking - Natural interactions
- Eye comfort - Avoid rapid movements