/visionos
Use when building Vision Pro apps — spatial computing, RealityKit 3D content, immersive spaces, or volumes.
$ npx -y skills add fusengine/agents --skill visionos --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/visionos
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when building Vision Pro apps — spatial computing, RealityKit 3D content, immersive spaces, or volumes.
SKILL.md
visionos.SKILL.mdname: visionos
description: Use when building Vision Pro apps — spatial computing, RealityKit 3D content, immersive spaces, or volumes.
versions:
visionos: 26
user-invocable: false
references: references/spatial-computing.md, references/realitykit.md, references/ornaments.md
related-skills: swift-core, swiftui-core, mcp-tools
<objective> Covers visionOS-specific development for Apple Vision Pro spatial computing: 3D spatial interaction, RealityKit-based 3D content rendering, immersive environments, mixed-reality features, and hand/eye tracking.
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. </objective>
visionOS Platform
visionOS-specific development for Apple Vision Pro spatial computing.
Agent Workflow (MANDATORY)
Before ANY implementation, use `TeamCreate` to spawn 3 agents:
1. **fuse-ai-pilot:explore-codebase** - Analyze existing visionOS patterns 2. **fuse-ai-pilot:research-expert** - Verify latest visionOS 26 docs via Context7/Exa 3. **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](references/spatial-computing.md) | | RealityView, 3D content | [realitykit.md](references/realitykit.md) | | Attachments, UI ornaments | [ornaments.md](references/ornaments.md) |
---
Best Practices
1. **Start with windows** - Familiar 2D first 2. **Add depth gradually** - Volumes for 3D 3. **Use ornaments** - Attach 2D UI to 3D 4. **Respect space** - Don't overwhelm user 5. **Hand tracking** - Natural interactions 6. **Eye comfort** - Avoid rapid movements
Read more
name: visionos description: Use when building Vision Pro apps — spatial computing, RealityKit 3D content, immersive spaces, or volumes. versions: visionos: 26 user-invocable: false references: references/spatial-computing.md, references/realitykit.md, references/ornaments.md related-skills: swift-core, swiftui-core, mcp-tools
<objective> Covers visionOS-specific development for Apple Vision Pro spatial computing: 3D spatial interaction, RealityKit-based 3D content rendering, immersive environments, mixed-reality features, and hand/eye tracking.
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. </objective>
visionOS Platform
visionOS-specific development for Apple Vision Pro spatial computing.
Agent Workflow (MANDATORY)
Before ANY implementation, use `TeamCreate` to spawn 3 agents:
1. **fuse-ai-pilot:explore-codebase** - Analyze existing visionOS patterns 2. **fuse-ai-pilot:research-expert** - Verify latest visionOS 26 docs via Context7/Exa 3. **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](references/spatial-computing.md) | | RealityView, 3D content | [realitykit.md](references/realitykit.md) | | Attachments, UI ornaments | [ornaments.md](references/ornaments.md) |
---
Best Practices
1. **Start with windows** - Familiar 2D first 2. **Add depth gradually** - Volumes for 3D 3. **Use ornaments** - Attach 2D UI to 3D 4. **Respect space** - Don't overwhelm user 5. **Hand tracking** - Natural interactions 6. **Eye comfort** - Avoid rapid movements
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill