# Arkit Visionos Developer

> Router for ARKit features on visionOS 27, including ARKitSession setup, authorization, provider selection, anchor processing, and RealityKit integration. Use when choosing an ARKit provider set, combining multiple ARKit providers, or troubleshooting shared ARKit lifecycle behavior before routing to focused provider skills.

- Skill: `tomkrikorian/arkit-visionos-developer` (Agent Skill, multi-file: 23 files)
- Install (CLI): `npx skillmds add tomkrikorian/arkit-visionos-developer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomkrikorian/arkit-visionos-developer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: tomkrikorian (https://skillmd.com/u/tomkrikorian)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/tomkrikorian/arkit-visionos-developer

---


# ARKit visionOS Developer

## Quick Start

1. If the task names a specific provider family, switch to the matching
   provider-focused skill below.
2. If the task spans provider families, load the provider index plus shared
   session and anchor references first.
3. Add only the usage strings, entitlements, and authorizations required by the
   providers you actually use.
4. Keep anchor state in a model layer, and bridge into RealityKit only when you
   have a rendering target.
5. If the issue is app launch, test flow, simulator behavior, or signing,
   switch to `build-run-debug` or `signing-entitlements`.

## Provider-Focused Skills

| Skill | When to Use |
|-------|-------------|
| `$arkit-spatial-tracking-providers` | World tracking, plane detection, scene reconstruction, room tracking, or shared coordinate spaces. |
| `$arkit-hand-tracking-provider` | Hand anchors, joint transforms, custom hand gestures, or hand visualizations. |
| `$arkit-reference-tracking-providers` | Known image tracking, object tracking, barcode detection, or accessory tracking. |
| `$arkit-camera-access-providers` | Camera frame streams or region-scoped camera content. |
| `$arkit-rendering-context-providers` | Environment lighting, stereo properties, device fit, or foveated field-of-view tuning. |

## Load Shared References When

| Reference | When to Use |
|-----------|-------------|
| [`references/provider-index.md`](references/provider-index.md) | When you need the provider map and routing guidance. |
| [`references/session-basics.md`](references/session-basics.md) | When setting up `ARKitSession`, authorization, or shared lifecycle rules. |
| [`references/anchor-processing.md`](references/anchor-processing.md) | When reconciling `anchorUpdates`, IDs, and model-layer state. |
| [`references/realitykit-bridge.md`](references/realitykit-bridge.md) | When ARKit data needs to become visible RealityKit scene content. |

## Workflow

1. Choose the provider family or focused skill.
2. Load the shared session and lifecycle guidance first.
3. Add only the provider references that match the task.
4. Keep anchor reconciliation in a model layer.
5. Bridge into RealityKit only after the model layer has stable state.

## Guardrails

- Keep a strong reference to `ARKitSession` for the full lifetime of the
  experience.
- Request authorization before running providers that need it.
- Do not block the main actor while awaiting provider updates.
- Do not assume every provider has the same presentation, privacy, entitlement,
  or provisioning requirements.
- Route launch, build, simulator, and codesign problems out to the execution
  skills instead of expanding this skill with run-loop detail.

## Output Expectations

Provide:
- the provider-focused skill or provider set chosen
- which shared and provider references were used
- the session and anchor-processing model
- the RealityKit bridge plan if applicable
- the next skill to use if the blocker is execution, signing, or scene work