Quest game workflow: start here

Made by Navid Mirzaaghazadeh · part of unity-meta-quest-skills · MIT

This skill only routes. The detailed steps live in the skills it names. Load the named skill before acting on a step.

• Plugin installs prefix skill names, for example quest-core:unity-cli. Match on the part after the colon.
• If a named skill isn't installed, say so and name the bundle that has it (see Bundles). Don't improvise its content from memory.

1. Before anything Quest-specific

1. Load hz-quest-verify-first. Quest APIs, manifest rules and store requirements change often, so check claims against Meta's live docs (metavr docs search "<topic>"), not memory.
2. Check the tools, and ask before installing anything that's missing:

   unity --version && unity status     # Unity CLI; an open Editor should show state "ready"
   metavr --version && metavr device list

   Missing tools → unity-quest-dev-setup (Unity CLI, Editor, Android modules) and metavr-cli (Meta VR CLI).
3. Prefer driving the open Editor (unity-cli, unity-pipeline: unity command run_script / eval; in Pipeline 0.9 script run / script eval, see skills/meta-official/ERRATA.md) over hand-editing .unity, .prefab or .asset YAML.

2. The path from idea to store

Also targeting Meta VR Glasses (ships spring 2027)

Same Horizon OS, Store and v207 SDKs as Quest, but eyes target, a pinch selects, controllers are sold separately, and the field of view is about 70° × 66°. Users without controllers see hand-tracked titles first. Decide at phase 0 whether controllers are required, optional or unsupported, then add these steps:

3. Hard rules

• Ask first before you upload to any release channel, use --publish, touch the LIVE or production channel, submit for review, install a tool, or change Claude or MCP config. Store submission itself happens in the Developer Dashboard, done by the user.
• Never commit or print secrets. Keystore passwords and app secrets come from environment variables. Remind the user to back up the keystore: without it the app can never be updated.
• Packaging baseline: IL2CPP, ARM64 only, targetSdkVersion 34 set explicitly (Unity's Meta Quest profile defaults to 32), and a version code that always increases.
• Conflicting values: Meta's hz-store-submit has outdated store specs (see ERRATA.md in the repo). The horizon-* skills hold the values checked on 2026-10-16. When in doubt, run metavr docs search.
• One of each: one interaction stack (Meta Interaction SDK or XRI), one build script, one verify-first skill (hz-quest-verify-first).
• Prove it on the device. Editor Play mode is not proof. Test on the headset or in the simulator, and read the logs (hz-vr-debug). Meta VR Glasses hardware isn't out yet: say which checks only the simulator covered.
• Experimental agent tools stay out of release builds. Meta XR Operator works only in Development builds, and Meta's in-Editor AI features run Claude Code with permissions bypassed; ask before enabling them.

4. Quick router

Bundles

When the library is installed as Claude Code plugins, skills come in five bundles: quest-core (this skill and the main path), meta-quest-extras (other Meta Unity features and tools), unity-extras (other official Unity skills), community-unity-xr and community-design-art. See the repository README for install commands. meta-vr-glasses-unity and hz-unity-device-readiness belong with the main path; meta-xr-operator-unity and the XR Simulator skills are in meta-quest-extras. Check the README if a skill isn't where this says.

Sources for the VR Glasses rows: https://developers.meta.com/vr/essentials/bring-your-app-glasses/ (2026-10-13), https://developers.meta.com/vr/documentation/unity/unity-support-meta-vr-glasses/ (2026-09-30), https://developers.meta.com/blog/meta-connect-recap-start-building-the-future-of-vr/ (2026-09-24).

Last verified: 2026-10-17