Spatial computing and XR development routing — Apple Vision Pro, visionOS, WebXR, AR/VR, Metal, spatial UI design, immersive controls, terminal integration. Use when the user asks about Vision Pro app development, visionOS APIs, WebXR/three.js, ARKit/RealityKit, spatial interaction patterns, immersive cockpit controls, hand tracking, eye tracking, mixed reality, or Metal-based 3D rendering on Apple platforms. Triggers on Vision Pro, visionOS, WebXR, ARKit, RealityKit, Metal, spatial UI, immer...
Scanned 8/31/2026
Install to Claude Code
Skills Directorynpx -y skills add daehounan/agency-agents-fork --skill xr-spatial-routing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Xr Spatial Routing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/daehounan-xr-spatial-routing)More formats (shields.io, HTML) on the badges page.
---
name: xr-spatial-routing
description: Spatial computing and XR development routing — Apple Vision Pro, visionOS, WebXR, AR/VR, Metal, spatial UI design, immersive controls, terminal integration. Use when the user asks about Vision Pro app development, visionOS APIs, WebXR/three.js, ARKit/RealityKit, spatial interaction patterns, immersive cockpit controls, hand tracking, eye tracking, mixed reality, or Metal-based 3D rendering on Apple platforms. Triggers on Vision Pro, visionOS, WebXR, ARKit, RealityKit, Metal, spatial UI, immersive, AR/VR/XR, hand tracking.
---
# XR Spatial Routing Skill
When this skill activates, route to the appropriate spatial-computing agent based on platform and concern.
## Routing matrix
| User signal | Agent to invoke |
|---|---|
| Spatial UX, interaction patterns, immersive UI | `xr-interface-architect` |
| visionOS native Swift app | `visionos-spatial-engineer` |
| macOS spatial / Metal / high-performance 3D | `macos-spatial-metal-engineer` |
| WebXR, browser-based AR/VR | `xr-immersive-developer` |
| Cockpit / control-surface XR | `xr-cockpit-interaction-specialist` |
| CLI / terminal tooling in XR context | `terminal-integration-specialist` |
## Combining with engineering agents
For Vision Pro apps involving network/backend work, also invoke `engineering-backend-architect` in parallel. For visionOS UI shipping production, pair with `engineering-frontend-developer` for any companion web surfaces.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
