Agent-Skills.md

Agent Skills: SharePlay Developer

Build, integrate, and troubleshoot SharePlay GroupActivities features, including GroupActivity definitions, activation flows, GroupSession lifecycle, messaging and journals, ShareLink and SharePlay UI surfaces, and visionOS spatial coordination. Use when implementing or debugging SharePlay experiences across Apple platforms, especially visionOS.

UncategorizedID: tomkrikorian/visionosagents/shareplay-developer

Repository

tomkrikorian/visionosagents
tomkrikorianLicense: MIT
475

Install this agent skill to your local

pnpm dlx add-skill https://github.com/tomkrikorian/visionOSAgents/tree/HEAD/skills/shareplay-developer

Skill Files

Browse the full folder contents for shareplay-developer.

Download Skill

Loading file tree…

skills/shareplay-developer/SKILL.md

Skill Metadata

Name
shareplay-developer
Description
Build, integrate, and troubleshoot SharePlay GroupActivities features for visionOS 26, including GroupActivity definitions, activation flows, GroupSession lifecycle, messaging and journals, ShareLink and SharePlay UI surfaces, and spatial coordination.

SharePlay Developer

Quick Start

  1. Decide whether this experience is launch-only co-location or shared state sync.
  2. Add the Group Activities capability and required entitlement before building SharePlay UI.
  3. Define one GroupActivity per experience and keep the payload minimal and Codable.
  4. Load the right reference only after you know the workflow.
  5. Configure SystemCoordinator before joining whenever spatial personas or immersive spaces are involved.

Load References When

| Reference | When to Use | |-----------|-------------| | activation-ui.md | When wiring the SharePlay entry point or start button flow. | | activity-definition.md | When defining the GroupActivity payload, metadata, or transfer representation. | | group-session-lifecycle.md | When joining, leaving, observing, or presenting a GroupSession. | | messaging-journal.md | When using GroupSessionMessenger, GroupSessionJournal, or late-joiner sync. | | spatial-coordination.md | When configuring SystemCoordinator, spatial templates, or group immersive-space behavior. | | visionos-immersive-space.md | When implementing launch-only SharePlay for a visionOS immersive space. | | groupactivities-patterns.md | When you need broader GroupActivities patterns or sample-backed examples. |

Workflow

  1. Define the activity and choose the activation surface.
  2. Observe and configure the session before joining.
  3. Add messaging or journal synchronization only if shared state is required.
  4. Configure spatial coordination when the experience shares an immersive space.
  5. Summarize the session lifecycle, sync model, and launch surface clearly.

When To Switch Skills

  • Switch to build-run-debug when the blocker is app launch, simulator state, or runtime debugging rather than SharePlay behavior.
  • Switch to signing-entitlements when the issue is capabilities, entitlements, or privacy gating.
  • Switch to telemetry when proof of event ordering or session state changes matters more than API design.

Guardrails

  • Keep GroupActivity data small and Codable.
  • Store strong references to GroupSession, GroupSessionMessenger, and GroupSessionJournal.
  • Configure SystemCoordinator before join() when using spatial coordination.
  • Do not treat .immersiveEnvironmentBehavior(.coexist) as the coordination API.
  • Join only after the UI and local state are ready.

Output Expectations

Provide:

  • the activity type and activation surface
  • the chosen session and sync model
  • which references were used
  • the coordination model if immersive space is involved
  • the next skill to use if the blocker is execution, signing, or testing