xr-dev

Shape: static. Fixed platform owners with an explicit lifecycle entry. The agent selects the earliest unresolved stage from repository and device evidence, then records the owner, prerequisites and next action instead of starting a competing delivery process.

quest-lifecycle

Use when planning, starting or auditing the full product lifecycle of a Meta Quest or Horizon OS game or app, including platform selection, immersive design, development milestones, publishing prerequisites, monetization, launch marketing and post-launch operation. Produces a stage/evidence/owner map and one next action. NOT for a single engine bug, capture analysis (quest-perf), upload (quest-store), or generic project delivery (task-pipeline).

quest-native

Use when building or reviewing a NATIVE Meta Quest / Horizon OS app in C or C++ against OpenXR — the Android manifest and Gradle contract, the Khronos OpenXR loader, session and frame loop, swapchains, Vulkan, passthrough, scene, hand tracking, and the SDK levels the Store now demands. NOT for Unity or Unreal engine implementation, not for a Kotlin Spatial SDK app, not for WebXR or a PWA (quest-webxr), not for profiling (quest-perf), not for Store submission (quest-store).

quest-spatial

Use when a Meta Quest app is built with Meta Spatial SDK — Kotlin and Android rather than Unity or raw OpenXR: whether that lane is right, the toolchain it demands, the ECS model, panels as real Android views, hybrid apps, the runtime budgets that decide a design, the known issues that waste a day, and which sample or documentation page answers a given question. NOT for native C++ OpenXR (quest-native), Unity (Meta's hz-unity-* skills), WebXR (quest-webxr), profiling a build (quest-perf), or Store submission (quest-store).

quest-perf

Use when a Meta Quest / Horizon OS app misses frames, judders, overheats or must be profiled — the frame budget per refresh rate, logcat stats, the GPU% number that lies during frame drops, Dynamic Resolution, foveation, Application SpaceWarp, and capturing with OVR Metrics, Perfetto, simpleperf or RenderDoc. Engine-independent. NOT for wiring the render loop itself (quest-native), not for Store performance VRCs as a submission gate (quest-store), and not for desktop or mobile-phone profiling.

quest-tooling

Use when setting up or driving the Meta Quest toolchain on a development machine - the metavr CLI and its MCP server, Meta's agentic skills, connecting a headset, installing the managed tools (Perfetto, RenderDoc, OVR Metrics, platform-utils, XR Simulator), and working with no headset at all. Also the hygiene - one install channel per agent, and no skill copies in a repository. NOT for writing app code (quest-native), reading a capture (quest-perf), or submitting a build (quest-store).

quest-store

Use when preparing Meta Quest testing, Meta Horizon Store submission, monetization, launch assets or post-launch commercial operation. Covers release channels, applicable VRCs, signing/manifest, account and data tasks, purchases/subscriptions, pre-launch listings, capture provenance and analytics. NOT for a whole-product roadmap (quest-lifecycle), app implementation, profiling (quest-perf), machine setup (quest-tooling), or PWA packaging (quest-webxr).

quest-webxr

Use when the XR experience runs in the browser rather than as a native binary - WebXR in the Meta Quest Browser, IWSDK or three.js or A-Frame, packaging the site as a PWA with the Meta Quest Bubblewrap CLI, in-app purchases through Horizon Billing, remote debugging with Chrome DevTools, and getting a PWA onto the Store. NOT for native OpenXR apps (quest-native), native profiling (quest-perf), or an APK submission (quest-store).