/hz-new-project-creation

name: hz-new-project-creation
license: Apache-2.0
description: "Scaffolds new Meta VR and Horizon OS projects after the build path is selected — Standard Android, Meta Spatial SDK, Unity, Unreal, or WebXR. Use when creating a new Meta VR app from scratch. Build paths: all; use hz-quest-verify-first to choose the path."
allowed-tools: Bash(metavr:*), Bash(hzdb:*), Bash(npx:*), mcp__metavr__metavr_unity_setup

New Project Creation Skill

Scaffold and configure new Meta VR projects from scratch after the build path has been selected. This skill provides step-by-step setup instructions with recommended settings optimized for Meta VR hardware.

When to Use This Skill

Use this skill when you need to:

• Create a brand-new project targeting Meta Quest (Quest 2, Quest 3, Quest 3S, Quest Pro) and Meta VR Glasses after selecting its build path
• Configure a project with the correct render settings, SDK versions, and build targets for Meta VR
• Set up a project template with recommended architecture and folder structure
• Follow the setup workflow for a previously selected Standard Android, Meta Spatial SDK, Unity, Unreal Engine, or WebXR project

Prerequisites

Before creating any Meta VR project, complete these steps regardless of platform:

1. **Create a Meta developer account** -- Sign up at [developer.meta.com](https://developer.meta.com) and create an organization. 2. **Set up your Meta VR device for development** -- Enable developer mode in the Meta Horizon app on your phone under your headset's settings. 3. **Enable USB debugging** -- Connect your Meta VR device via USB-C, put on the headset, and accept the "Allow USB debugging" prompt. 4. **Install metavr** -- Install the standalone `metavr` CLI binary on your PATH (see the `metavr-cli` skill), or invoke it on demand via `npx` with no install:

   metavr --version

Examples below use the bare `metavr` command; if you use the npm distribution, prefix with `npx -y`.

Verify your device connection before starting any project:

metavr device list

Start with the selected build path

Use `hz-quest-verify-first` to identify the build path before scaffolding. Do not choose an SDK from a feature checklist: several paths can expose similar Meta VR features, but they have different project structures and runtime models.

| Build path | Choose it when | Setup reference or skill | |---|---|---| | Standard Android | The app is primarily 2D UI in one resizable Horizon OS panel, implemented with Jetpack Compose, Android Views, React Native, or Expo. This is the default for a new 2D app; Spatial SDK is not required. | [Standard Android project](references/android-project.md); use `hz-react-native-expo` for React Native or Expo | | Meta Spatial SDK | The app needs an immersive scene, 3D entities, environment control, or hybrid 2D-and-3D content. | [Spatial SDK project](references/spatial-sdk-project.md) | | Unity | The app is an immersive game or experience built in C#. | [Unity project](references/unity-project.md) | | Unreal Engine | The app is an immersive project built with C++ or Blueprints. | [Unreal project](references/unreal-project.md) | | IWSDK / WebXR | The experience is web-based and should run in the browser or ship as a web app. | [Web project](references/web-project.md) |

After Choosing a Platform

Once the user has selected a platform, refer to the corresponding reference guide for detailed, step-by-step project setup:

• **Unity (Meta VR)** -- **MUST** use the `metavr_unity_setup` MCP tool to create the project. Do NOT run Unity CLI directly. Do NOT walk the user through manual Package Manager / XR Plug-in Management steps. See [Unity Project Setup](references/unity-project.md). Manual fallback at [unity-project-manual.md](references/unity-project-manual.md) only when the MCP tool is unavailable. (Note: this guidance applies to **Meta VR** Unity projects only — for non-VR Unity projects use Unity Hub as normal.)
• **Unreal Engine** -- [Unreal Project Setup](references/unreal-project.md)
• **Standard Android** -- [Standard Android Project Setup](references/android-project.md); use `hz-react-native-expo` when the UI is implemented with React Native or Expo
• **Meta Spatial SDK** -- [Spatial SDK Project Setup](references/spatial-sdk-project.md)
• **Web / IWSDK / WebXR** -- [Web Project Setup](references/web-project.md)

Each reference covers:

1. Required tool and SDK versions 2. Project creation steps 3. Recommended project settings for Meta VR 4. Build and deployment workflow 5. Testing and iteration workflow

Gotchas

These are common pitfalls when setting up new Meta VR projects.

• **Android API level mismatch** -- For new immersive projects, start with minimum API 32 and target API 34. Check `hz-store-submit` for the minimum store-acceptance floor and `hz-api-upgrade` for the current target range; immersive and 2D panel apps differ. Setting the wrong API level is a common reason builds fail to install or upload. Unity defaults may not match these requirements — always verify in Player Settings > Other Settings and with `metavr docs search "target API"`.
• **ARM64 only, no x86** -- Meta VR devices are ARM64 (aarch64). If your build pipeline targets x86 or includes x86 native libraries, the APK will install but crash immediately on launch. In Unity, ensure "Target Architectures" has only ARM64 checked. In Android Studio, verify your ABI filters.
• **Gradle version compatibility** -- Meta's Android and Spatial SDK samples often pin compatible Gradle, Android Gradle Plugin, Kotlin, and KSP versions. Copy the complete version set from a current official template or sample; upgrading one independently can cause obscure build failures.
• **Unity version matters** -- Not every Unity version is compatible with the latest Meta XR SDK. Check the Meta XR SDK release notes for the supported Unity version range. Using an unsupported Unity version causes cryptic C# compilation errors or missing