how a Quest product moves from platform choice to launch and operation
xr-dev
Quest product delivery from platform choice to launch and operation, with stage owners, evidence gates and next actions. quest-lifecycle connects immersive design, engine discovery, account readiness, development, capture and launch planning. quest-native covers C/C++ OpenXR and MR capability boundaries; quest-spatial covers Kotlin, ECS, measured panel budgets and hybrid activities; quest-perf covers rendering experiments and sustained device performance; quest-tooling covers current-source research and CLI/MCP discovery; quest-store covers submission, monetization, Store assets and growth; quest-webxr covers browser and packaged PWA delivery. Engine-specific Meta companions and official Godot XR documentation remain separate sources, with explicit fallbacks when tools or devices are absent.
Install this pack on its own, or use it with the ssheleg harness.
What it ships
Each name below is an entry point an agent can be routed to.
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 or auditing a Quest or Horizon OS product from platform choice to operation, as a stage, evidence and owner map. NOT for one engine bug, profiling (quest-perf), upload (quest-store) or delivery (task-pipeline). Opt out: no xr xr.
quest-native
Use when building or reviewing a native Quest app in C/C++ on OpenXR: manifest, frame loop, swapchains, Vulkan, passthrough. NOT for Unity/Unreal, Spatial SDK (quest-spatial), WebXR (quest-webxr) or profiling (quest-perf). Opt out: no xr xr.
quest-spatial
Use when a Meta Quest app is built with Meta Spatial SDK in Kotlin: lane fit, toolchain, ECS, panels as Android views, hybrid apps. NOT for native OpenXR (quest-native), Unity, WebXR (quest-webxr) or profiling (quest-perf). Opt out: no xr xr.
quest-perf
Use when a Meta Quest app drops frames, overheats or needs profiling: frame budgets, foveation, SpaceWarp, OVR Metrics, Perfetto, RenderDoc. NOT for the render loop (quest-native) or non-Quest profiling. Opt out: no xr xr.
quest-tooling
Use when setting up or driving the Meta Quest toolchain on a dev machine: metavr CLI and MCP, Meta's agent skills, a connected headset, XR Simulator. NOT for app code (quest-native), captures (quest-perf) or submission (quest-store). Opt out: no xr xr.
quest-store
Use when preparing Meta Quest testing, Horizon Store submission, monetization, launch or post-launch operation (release channels, VRCs). NOT for a roadmap (quest-lifecycle), profiling (quest-perf) or PWA packaging (quest-webxr). Opt out: no xr xr.
quest-webxr
Use when the XR experience runs in the Meta Quest Browser: WebXR with IWSDK, three.js or A-Frame, Bubblewrap PWA, Horizon Billing. NOT for native OpenXR (quest-native), APK submission (quest-store) or flat three.js (web3d-dev). Opt out: no xr xr.
Follow the Quest product lifecycle →
Stage map, engine paths and immersive design acceptance, with separate evidence for build, device, Store and operation.
Install just this one
Every pack installs standalone. The whole family is one command.
npx skills add ssheleg/xr-dev
claude plugin marketplace add ssheleg/xr-dev && claude plugin install xr-dev@xr-dev
When the agent reaches for it
These are the rules the family writes into your agent's own instruction file, verbatim. Each one states the rule, the boundary in both directions, and the phrase that declines it.
/xr-dev: how a Quest product moves from platform choice to launch and operation
- when: the thing being built runs on a Meta Quest headset
- decline it: no xr
If xr-dev is installed, Meta Quest products go through it: native OpenXR/Spatial SDK/WebXR choice, frame budget per refresh rate, toolchain, headset, Store submission, monetization, launch and operation. quest-lifecycle maps each stage to an owner, evidence and next action.
The boundary. NOT through it: ordinary browser 3D (web3d-dev), phone/desktop apps, Unity/Unreal internals (vendor skills), delivery (task-pipeline).
Refusal phrase: "no xr" or «без xr».
Among the routers: web3d-dev owns web scenes; xr-dev their headset lifecycle. A three.js scene in Quest Browser takes both.
The rest of the family
super-ux v0.67.1
Scenario-driven UI development: a versioned design chain in docs/ux/ — the product vision, personas and jobs, user flows and the paid-acquisition funnel among them, a screens-and-states map with Figma frames…
task-pipeline v1.105.1
Full-cycle delivery orchestrator: an intake grill turns the request into a complete brief, then ten gated stages carry it from docs to acceptance, refusing to advance until each gate passes.
agent-sync v1.23.6
Coordination plane for concurrent agents: leases with a TTL so two agents cannot claim the same work, race-free id reservation, a run journal and a generated board, over a pluggable knowledge cloud.
make-skill v0.33.6
A skill that builds skills: create, retrofit, audit and publish agent skills and Claude Code plugins
sheleg-design v1.66.6
The taste layer: cinematic scroll-driven landing pages (one scroll clock, motion that degrades to calm, WebGL particle formations), product-UI style packs with a ready token layer each, and the Figma border
seo-aeo-audit v0.32.5
Evidence-first website audit for search and answer engines: ten tracks from crawl access to AI citation mechanics, every finding backed by an observation and every recommendation tiered, ending in…
sheleg-dev v0.16.4
The integration layer a product reaches once it has users: Stripe subscription billing reconciled into your own database
agent-stack v0.32.1
Production patterns for AI agent systems, in four skills. The orchestrator: tool-calling loops that survive context pressure, pipelines with human checkpoints and resume, provider routing with fallback…
telegram-dev v0.5.5
Telegram, split by the API each surface actually speaks, in three skills. telegram-bots covers the official HTTP Bot API
web3d-dev v0.2.8
Realtime 3D on the web with three.js and React Three Fiber, in three skills split by the question. web3d-runtime owns how the scene runs