mcpField
V
visionos-immersive-media-developer

visionos-immersive-media-developer

github.com/tomkrikorianDevelopment6689 installsUpdated 19w ago
Repository

About visionos-immersive-media-developer

A visionOS development skill for choosing and implementing immersive media playback architectures. It helps developers match media types to AVKit or RealityKit surfaces and account for scene transitions, playback events, and comfort.

Key features

  1. 01Choose playback architecture
  2. 02Select viewing modes by media type
  3. 03Handle scene and mode transitions
  4. 04Use playback events for UI and rendering
  5. 05Plan comfort mitigation

Use cases

  1. 01Choosing window, portal, or immersive playback
  2. 02Building a custom RealityKit video surface
  3. 03Managing transitions between viewing modes
  4. 04Responding to playback readiness and comfort issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tomkrikorian/visionosagents --skill visionos-immersive-media-developer

After installing, type/visionos-immersive-media-developerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
apmp-and-spatial-video.md
apple-immersive-video-authoring.md
avexperiencecontroller.md
avkit-visionos-playback.md
comfort-mitigation.md
immersive-viewing-modes.md
playback-decision-tree.md
video-player-events.md
videoplayercomponent-basics.md

Details

From the project README

visionOS Immersive Media Developer

Quick Start

Decide first whether the app should use the system AVKit experience or a custom RealityKit playback surface.

  1. Clarify the media shape: surface video, portal, progressive immersive, full immersive, spatial video, or Apple Immersive Video.
  2. Load only the matching reference files.
  3. Treat playback-mode changes as both media and scene-orchestration work.

Load References When

ReferenceWhen to Use
playback-decision-tree.mdDecision tree: window vs portal vs progressive vs full immersive playback.
avkit-visionos-playback.mdWhen using AVKit AVPlayerViewController and AVExperienceController as the system playback surface.
avexperiencecontroller.mdWhen AVKit AVExperienceController is the right surface for the product.
videoplayercomponent-basics.mdWhen you need to set up VideoPlayerComponent + AVPlayer correctly.
video-player-events.mdWhen RealityKit video playback must drive UI, scene transitions, rendering readiness, or comfort mitigation from VideoPlayerEvents.
apmp-and-spatial-video.mdWhen the content is spatial video, APMP, or Apple Immersive Video.
immersive-viewing-modes.mdWhen implementing portal, progressive, or full modes and related scene transitions.
comfort-mitigation.mdWhen handling comfort violations and mitigation strategies.
apple-immersive-video-authoring.mdWhen you need Apple Immersive Video authoring or packaging references.

Workflow

  1. Choose the playback architecture.
  2. Load the references for that surface and media type.
  3. Implement playback and viewing-mode transitions.
  4. Add event handling and comfort mitigation where relevant.
  5. Summarize the playback path, transition model, and remaining validation work.

Guardrails

  • Start with AVKit AVExperienceController when the system player experience fits the product.
  • Use RealityKit VideoPlayerComponent when the video must live in a custom scene graph.
  • Do not treat immersive-mode transitions as a simple property flip when the app also needs scene changes.
  • Make sure the user has a clear exit path from immersive playback.

Output Expectations

Provide:

  • the chosen playback architecture
  • the media type and viewing mode
  • which references were used
  • the transition or event model involved
  • the next validation step

Comments

Markdown supported