@ssheleg/xr-dev 0.3.0

package/CHANGELOG.md

@@ -0,0 +1,143 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the project uses
+[semantic versioning](https://semver.org/spec/v2.0.0.html).
+
+## 0.3.0 — 2026-09-21
+
+- Add quest-lifecycle: a portable product-stage map with proactive next actions, engine selection, immersive-design acceptance and evidence gates.
+- Extend all six existing owners with platform/research/rendering coverage, cooperative hybrid activities, source-conflict handling, commercial readiness, capture and Store asset production, and post-launch analytics.
+- Correct stale descriptions, hard Spatial limits, CPU/GPU timing claims, release manifest guidance and duplicate MCP setup defaults. Keep current SDK/device/Dashboard checks explicit.
+- Add lifecycle evaluation cases and record isolated baseline/candidate planning probes separately from routing, build and headset verification.
+
+
+## [0.2.1] — 2026-09-20
+
+### Changed
+
+- `quest-spatial`'s description trimmed to 882 characters. It shipped at 955 and
+  moved the family's reserve ratchet — the 60 characters below the 970 cap exist
+  for the "NOT for" clause the next neighbouring skill will force, and this pack
+  now sits beside Meta's `hz-spatial-sdk`, which is exactly such a neighbour.
+- The card the umbrella generates for this member, regenerated from the new
+  manifest.
+
+## [0.2.0] — 2026-09-20
+
+### Added
+
+- **`quest-spatial`** — the Kotlin lane. Meta Spatial SDK is how an Android team
+  reaches Horizon OS, and the pack had no answer for it: which lane it is right
+  for, the toolchain it demands (Horizon OS v69+, AGP 8.11.1 under the Gradle
+  9.4.1 wrapper, Kotlin 2.1.0, JDK 17, Spatial Editor for all but two samples),
+  and the budgets that decide a design rather than tune it — 2,000 entity
+  operations per tick, 500 physics objects, ~1,000 scene-graph entities, and a
+  panel table whose sharpest rows are three video panels and two activity-based
+  ones.
+- Its three references: `samples-map.md` (15 official samples mapped to the
+  question each answers, plus the `hzdb` MCP server a clone brings with it),
+  `docs-map.md` (197 pages, by prefix and by topic), `budgets-and-traps.md`
+  (the tables, and the five issues Meta lists against itself — including debug
+  builds being slow enough to invalidate a measurement, and `finish()` on an
+  immersive activity crashing inside `libMetaSpatialSDK.so`).
+
+### Changed
+
+- The pack now routes six lanes, not five; Meta's `hz-spatial-sdk` still owns
+  the implementation of a Spatial SDK app, and `quest-spatial` says when to be
+  there at all and where to read.
+
+## [0.1.5] — 2026-09-20
+
+### Fixed
+
+- `test/social_preview.py`, the last CI step this repository inherited a job for
+  and never inherited the script for. Every step of both jobs has now been run
+  locally against this tree before the push, which is how the previous two
+  failures should have been caught.
+
+## [0.1.4] — 2026-09-20
+
+### Fixed
+
+- CI was red on the first push and the repository did not know it: the online
+  schema check imports `SCHEMA_FOR` from the validator, which exported only an
+  internal `SCHEMAS` map, and the audit job ran a `test/evals_validate.py` that
+  had never been copied in. Both closed — the pinned addresses now live in one
+  map that both halves read, and the eval data validates with its own planted
+  defect.
+
+### Added
+
+- `test/evals/README.md` and `RESULTS.md`. Results says, in as many words, that
+  no model run has happened yet: an unrun eval reported as a pass is worse than
+  no eval.
+- The trigger split now carries **both classes in each half** — a train split of
+  positives only cannot show over-firing, which is the failure mode that matters
+  beside Meta's 29 neighbouring skills.
+
+## [0.1.3] — 2026-09-20
+
+### Added
+
+- `docs/assets/social-preview.png` — the card the family umbrella generates for
+  this member from `skills.json`, byte-compared in its suite so the pixels and
+  the manifest cannot drift apart.
+
+## [0.1.2] — 2026-09-20
+
+### Added
+
+- `docs/AGENT_SYNC.md`, generated from the live coordination config, and a
+  repository `CLAUDE.md` that links it and states the invariants each gate
+  checks. A guarded-file list no agent instruction points at is a list nobody
+  reads.
+
+## [0.1.1] — 2026-09-20
+
+### Changed
+
+- `quest-tooling`'s description trimmed back inside the 60-character reserve the
+  family keeps below the 970 cap — the room a near-miss neighbour's "NOT for"
+  clause will need.
+- README says where its verification commands run: a clone, not the published
+  package, which ships the skills without `test/`.
+
+### Added
+
+- `.claude/agent-sync.json`, so a second agent in this repository claims the
+  guarded files instead of overwriting them.
+
+## [0.1.0] — 2026-09-20
+
+First release. Five skills, seven references.
+
+### Added
+
+- `quest-native` — the native OpenXR lane: development versus release manifest,
+  SDK levels including the 1 March 2026 target-34 rule, the Khronos loader and
+  its two initialisation extensions, the frame loop and the focus rules review
+  enforces, capability checks over device models.
+- `quest-perf` — per-refresh-rate frame budgets, the `GPU%` reading that falls
+  exactly when an app is GPU-bound and the 50% threshold behind it, the four
+  recovery levers in order, and a capture playbook for Perfetto, simpleperf,
+  RenderDoc and OVR Metrics through `metavr`.
+- `quest-tooling` — the metavr CLI surface, its MCP server and how one server
+  ends up registered twice, `metavr init`'s all-agents default measured at 4129
+  files inside a repository, the managed tool matrix, and the hygiene rules.
+- `quest-store` — the four release channels and what review actually checks,
+  the VRC list generated from Meta's page (80 requirements, 14 groups), the
+  release manifest delta, uploading with `metavr store dist`.
+- `quest-webxr` — requesting an immersive session on load, IWSDK versus three.js
+  versus A-Frame, Bubblewrap packaging with the Digital Asset Links step, and
+  the performance honesty a browser build needs.
+
+[0.2.1]: https://github.com/ssheleg/xr-dev/releases/tag/v0.2.1
+[0.2.0]: https://github.com/ssheleg/xr-dev/releases/tag/v0.2.0
+[0.1.5]: https://github.com/ssheleg/xr-dev/releases/tag/v0.1.5
+[0.1.4]: https://github.com/ssheleg/xr-dev/releases/tag/v0.1.4
+[0.1.3]: https://github.com/ssheleg/xr-dev/releases/tag/v0.1.3
+[0.1.2]: https://github.com/ssheleg/xr-dev/releases/tag/v0.1.2
+[0.1.1]: https://github.com/ssheleg/xr-dev/releases/tag/v0.1.1
+[0.1.0]: https://github.com/ssheleg/xr-dev/releases/tag/v0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 ssheleg
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,98 @@
+# xr-dev — Meta Quest product lifecycle, seven skills
+
+Agent skills for taking Quest games and apps from platform choice to release and
+operation. Each stage names its owner, evidence and next action, so the agent can
+surface account, design, performance and launch work before it becomes a blocker.
+
+Part of the [ssheleg harness](https://skills.sshlg.me/harness/). This pack works
+independently and composes with the family delivery, UX and design skills.
+
+## The seven skills
+
+| Skill | Answers |
+|---|---|
+| [quest-lifecycle](plugins/xr-dev/skills/quest-lifecycle/SKILL.md) | What stage is this product at, what is missing, and what should happen next? |
+| [quest-native](plugins/xr-dev/skills/quest-native/SKILL.md) | How is the C/C++ OpenXR project built and audited, including MR capability and lifecycle boundaries? |
+| [quest-spatial](plugins/xr-dev/skills/quest-spatial/SKILL.md) | How do Kotlin Spatial SDK, ECS, panels and hybrid activities fit this app? |
+| [quest-perf](plugins/xr-dev/skills/quest-perf/SKILL.md) | What limits frames, memory or sustained performance, and which rendering experiment tests it? |
+| [quest-tooling](plugins/xr-dev/skills/quest-tooling/SKILL.md) | Which tools and sources are available, current and appropriate for this host? |
+| [quest-store](plugins/xr-dev/skills/quest-store/SKILL.md) | What remains for testing, submission, monetization, Store assets, launch and operation? |
+| [quest-webxr](plugins/xr-dev/skills/quest-webxr/SKILL.md) | How does the browser/PWA experience handle sessions, optional features and delivery? |
+
+References live inside their owning skill and load on demand. The skill bodies
+link every shipped reference with a use condition. For the complete change and
+verification record, see [lifecycle release evidence](docs/evidence/verification/2026-09-21-lifecycle/README.md).
+
+## Start with the product stage
+
+For a new or inherited product, invoke `/quest-lifecycle` from a skills directory
+or `/xr-dev:quest-lifecycle` from the plugin. It inspects the actual engine and app
+category, preserves existing project records, and proposes the earliest unresolved
+step. For a single bug, capture or upload, use that specialist directly.
+
+The workflow covers platform selection, immersive UX, a device-tested vertical
+slice, content/performance budgets, commercial prerequisites, real gameplay
+capture, Store review and post-launch checks. It distinguishes 2D, immersive,
+hybrid, WebXR, packaged PWA and PC VR requirements.
+
+[Meta's own companion skills](https://github.com/meta-quest/agentic-tools) supply
+engine and tool workflows when installed. The lifecycle engine map also points
+to Godot's official XR/export/vendor-plugin documentation. This pack supplies
+fallback procedures; it does not install an engine, promise every device feature,
+or treat a generated image as gameplay evidence.
+
+## Install
+
+Claude Code plugin:
+
+```text
+/plugin marketplace add ssheleg/xr-dev
+/plugin install xr-dev@xr-dev
+```
+
+Portable Agent Skills:
+
+```bash
+npx skills add ssheleg/xr-dev
+```
+
+The standalone npm installer also works when the same Claude plugin is absent:
+
+```bash
+npx @ssheleg/xr-dev --help
+```
+
+Use one channel per agent. For a composing family installation, update through
+`npx sshlg-skills update`. Restart the agent after updates so skills reload.
+
+## Tools and source freshness
+
+Inspect existing CLI/MCP/plugin registration before setup. `quest-tooling` maps
+Meta VR CLI, device/debug/profiling tools and Markdown documentation indexes,
+with the operator's gateway policy taking precedence over generic setup examples.
+No MCP uses CLI; no CLI uses official docs; absent engine/device/account access
+leaves dependent checks explicitly unverified. An HTTP 200 may be an unavailable
+page, and a source example is not a universal SDK or Store requirement.
+
+## Verifying a change
+
+<!-- commands-run-in: a clone -->
+The repository carries tests; the npm payload carries the skills and references.
+
+```bash
+npm test
+npm run test:negatives
+node test/installer_test.js
+python3 test/evals_validate.py
+claude plugin validate . --strict
+claude plugin validate plugins/xr-dev --strict
+```
+
+[Test evaluation documentation](test/evals/README.md) separates scenario definitions,
+isolated model planning probes, runtime routing and device/product evidence.
+
+## License
+
+MIT for this pack. Primary documentation is linked and dated; third-party tools,
+assets and models retain their own licenses. Recheck volatile requirements before
+implementation and submission.

package/SECURITY.md

@@ -0,0 +1,39 @@
+# Security
+
+## Reporting
+
+Report anything sensitive privately to **security@sshlg.me**, not in a public
+issue. Include the file, what happens, and what you expected.
+
+## What executes when you install this
+
+| Path | Runs when | What it touches |
+|---|---|---|
+| `bin/xr-dev.js` | `npx @ssheleg/xr-dev` | copies the skill directories into `~/.claude/skills/<name>`; refuses (exit 3) when the plugin is already installed; writes nothing else |
+| `install.sh` | run by hand | the same copy, in POSIX shell |
+| `test/*.py`, `test/*.js` | only in CI or by hand | read the repository; `check_schemas.py` makes outbound HTTPS requests to schemastore.org |
+
+The skills themselves ship **no hooks, no MCP server and no background
+process**. Nothing here runs at session start.
+
+## What the skills tell an agent to run
+
+The bodies name `metavr`, `adb`, `keytool`, `bubblewrap`, `npm` and `git`
+commands. Two classes deserve attention before an agent runs them unattended:
+
+- **Device-mutating**: `metavr app install|uninstall`, `metavr files rm`,
+  `metavr device configure-testing`, `metavr shell`. They act on a connected
+  headset.
+- **Outward-facing**: `metavr store dist upload` and `copy-build` put a build in
+  front of testers or the Store. Uploads default to a **draft**; `--publish` is
+  the flag that makes it visible. Treat both as actions needing a human's say-so.
+
+No skill asks an agent to bypass a consent prompt, and no skill fetches its own
+instructions from a URL at runtime.
+
+## Credentials
+
+Nothing in this repository stores or reads a credential. `metavr auth login`
+keeps its token in the OS keychain; `METAVR_TOKEN` exists for CI. Signing
+keystores belong outside the repository, and every skill that mentions one says
+so.

package/bin/xr-dev.js

@@ -0,0 +1,186 @@
+#!/usr/bin/env node
+/*
+ * xr-dev installer CLI.
+ *
+ * Installs every xr-dev skill into ~/.claude/skills/<name>
+ * (same layout as install.sh). Idempotent: an existing install is skipped unless
+ * --force. Zero dependencies.
+ *
+ * For other agents (Cursor, Codex, 70+) use: npx skills add ssheleg/xr-dev
+ */
+'use strict';
+
+const fs = require('fs');
+const path = require('path');
+const os = require('os');
+
+const ROOT = path.resolve(__dirname, '..');
+const REPO = 'ssheleg/xr-dev';
+const PLUGIN = 'xr-dev';
+
+// Exit codes are the contract: 0 installed or skipped, 1 corrupted package,
+// 2 usage error, 3 refused — the plugin channel owns this agent (--force overrides).
+const EXIT_PLUGIN_PRESENT = 3;
+
+/**
+ * The plugin spec (`<name>@<marketplace>`) installed for `name` in this home,
+ * or null.
+ *
+ * `installed_plugins.json` is the record of what is actually installed. The
+ * `plugins/marketplaces/<name>` directory — the only signal older family
+ * installers read — under-reports: a marketplace added from a local `directory`
+ * source has no dir there at all, and plugin names differ from marketplace
+ * names, so a check keyed on it stays green while the shadow lands. Absence
+ * and corruption both read as "no plugin": the fresh HOME is the common case,
+ * and an installer that crashes on a parse error refuses the machines that
+ * need it most.
+ */
+function installedPluginSpec(home, name) {
+  try {
+    const raw = fs.readFileSync(
+      path.join(home, '.claude', 'plugins', 'installed_plugins.json'), 'utf8');
+    const parsed = JSON.parse(raw);
+    const plugins =
+      parsed && typeof parsed === 'object' &&
+      parsed.plugins && typeof parsed.plugins === 'object'
+        ? parsed.plugins
+        : parsed;
+    if (!plugins || typeof plugins !== 'object') return null;
+    for (const spec of Object.keys(plugins)) {
+      if (spec === name) return `${name}@${name}`;
+      if (spec.startsWith(name + '@')) return spec;
+    }
+  } catch {
+    // missing or corrupt = no plugin — fail open on absence, never crash
+  }
+  return null;
+}
+
+function usage() {
+  console.log(`xr-dev installer
+
+Usage:
+  npx @ssheleg/xr-dev [--force]   install all xr-dev skills
+                                       into ~/.claude (skip existing unless --force)
+  npx @ssheleg/xr-dev --help
+
+Exit codes:
+  0 installed or skipped   2 usage error
+  1 corrupted package      3 refused: the xr-dev PLUGIN is installed in
+                             this home — plain copies would shadow it (pass
+                             --force to write them anyway)
+
+Other install paths:
+  Claude Code plugin:  /plugin marketplace add ${REPO}
+                       /plugin install xr-dev@xr-dev
+  Any agent (70+):     npx skills add ${REPO}`);
+}
+
+function copyDir(src, dest) {
+  fs.mkdirSync(dest, { recursive: true });
+  for (const entry of fs.readdirSync(src, { withFileTypes: true })) {
+    const s = path.join(src, entry.name);
+    const d = path.join(dest, entry.name);
+    if (entry.isDirectory()) copyDir(s, d);
+    else fs.copyFileSync(s, d);
+  }
+}
+
+function installOne(label, src, dest, isDir, force) {
+  if (fs.existsSync(dest) && !force) {
+    console.log(`skip: ${label} already installed at ${dest} (rerun with --force to overwrite)`);
+    return;
+  }
+  fs.rmSync(dest, { recursive: true, force: true });
+  fs.mkdirSync(path.dirname(dest), { recursive: true });
+  if (isDir) copyDir(src, dest);
+  else fs.copyFileSync(src, dest);
+  console.log(`Installed ${label} -> ${dest}`);
+}
+
+function main(argv) {
+  const args = argv.slice(2);
+  if (args.includes('--help') || args.includes('-h')) {
+    usage();
+    return 0;
+  }
+  const force = args.includes('--force');
+  const unknown = args.filter((a) => a !== '--force');
+  if (unknown.length) {
+    console.error(`unknown argument(s): ${unknown.join(' ')}`);
+    usage();
+    return 2;
+  }
+
+  const skillsRoot = path.join(ROOT, 'plugins/xr-dev/skills');
+  if (!fs.existsSync(skillsRoot)) {
+    console.error(`error: skill sources missing at ${skillsRoot} — corrupted package?`);
+    return 1;
+  }
+
+  const names = fs
+    .readdirSync(skillsRoot, { withFileTypes: true })
+    .filter((e) => e.isDirectory())
+    .map((e) => e.name)
+    .sort();
+  if (!names.length) {
+    console.error(`error: no skills found under ${skillsRoot} — corrupted package?`);
+    return 1;
+  }
+
+  const home = os.homedir();
+
+  // One channel per agent. A plain ~/.claude/skills/<name> beside an installed
+  // plugin is two listings of the same skill, and the stale copy wins — the
+  // exact shadow the family canon forbids. Refuse rather than create it, and
+  // refuse LOUDLY: reproduced live 2026-08-29 ON THIS PACKAGE — a bare
+  // `npx @ssheleg/xr-dev` shipped all three skills as plain copies into
+  // the operator's ~/.claude/skills/ while the xr-dev plugin was
+  // enabled, because until v0.1.9 nothing here looked. A refusal that exits 0
+  // reads as success to every script above it, so this one exits 3.
+  const spec = installedPluginSpec(home, PLUGIN);
+  const marketplace = path.join(home, '.claude', 'plugins', 'marketplaces', PLUGIN);
+  const viaMarketplaceDir = !spec && fs.existsSync(marketplace);
+  if ((spec || viaMarketplaceDir) && !force) {
+    const found = spec
+      ? `installed as the Claude Code plugin ${spec}\n` +
+        '         (declared in ~/.claude/plugins/installed_plugins.json)'
+      : `registered as a Claude Code marketplace\n         (${marketplace})`;
+    console.error(
+      `refused: xr-dev is already ${found}.\n` +
+      "         Plain copies in ~/.claude/skills/ would shadow the plugin's skills\n" +
+      '         and serve this frozen version forever. Update the plugin channel\n' +
+      '         instead:\n' +
+      '           claude plugin marketplace update xr-dev\n' +
+      `           claude plugin update ${spec || 'xr-dev@xr-dev'}\n` +
+      '         Family launcher (updates every member, prunes shadow copies):\n' +
+      '           npx --yes sshlg-skills@latest update\n' +
+      '         Pass --force to write the plain copies anyway — a deliberate choice\n' +
+      '         to run two channels, where the stale one wins.'
+    );
+    return EXIT_PLUGIN_PRESENT;
+  }
+
+  for (const name of names) {
+    installOne(
+      `${name} skill`,
+      path.join(skillsRoot, name),
+      path.join(home, '.claude', 'skills', name),
+      true,
+      force
+    );
+  }
+
+  // The last line says how the next version arrives — "Installed" is not a
+  // complete sentence. Auto-update is off on purpose: this member composes
+  // with its family, and per-marketplace autoUpdate moves each member on its
+  // own clock, into combinations nobody tested together.
+  console.log(
+    '\nUpdates: rerun `npx @ssheleg/xr-dev@latest --force`, or refresh the\n' +
+    'whole family with `npx --yes sshlg-skills@latest update` (every channel,\n' +
+    'and it prunes plain copies that would shadow a plugin).'
+  );
+  return 0;
+}
+
+process.exit(main(process.argv));

package/package.json

@@ -0,0 +1,56 @@
+{
+  "name": "@ssheleg/xr-dev",
+  "version": "0.3.0",
+  "description": "Seven skills for the Meta Quest product lifecycle: platform and engine discovery, immersive design, native OpenXR, Kotlin Spatial and hybrid apps, WebXR/PWA, rendering experiments, tool and source discovery, Store submission, monetization, launch assets and post-launch operation. Agents receive stage-specific next actions, evidence gates and fallbacks when tools or devices are absent. Engine specialists remain separate; live requirements are verified against current Meta documentation.",
+  "bin": {
+    "xr-dev": "bin/xr-dev.js"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "files": [
+    "bin",
+    "plugins",
+    "README.md",
+    "LICENSE",
+    "CHANGELOG.md",
+    "SECURITY.md"
+  ],
+  "repository": "github:ssheleg/xr-dev",
+  "homepage": "https://skills.sshlg.me/skills/xr-dev/",
+  "license": "MIT",
+  "author": {
+    "name": "ssheleg",
+    "url": "https://x.com/sshlg93"
+  },
+  "engines": {
+    "node": ">=16"
+  },
+  "keywords": [
+    "agent-skills",
+    "android-ndk",
+    "ar",
+    "bubblewrap",
+    "claude-code",
+    "cursor",
+    "horizon-os",
+    "kotlin",
+    "meta-quest",
+    "metavr",
+    "mruk",
+    "openxr",
+    "perfetto",
+    "pwa",
+    "quest",
+    "renderdoc",
+    "spatial-sdk",
+    "vr",
+    "vulkan",
+    "webxr",
+    "xr"
+  ],
+  "scripts": {
+    "test": "python3 test/validate.py",
+    "test:negatives": "python3 test/validate.py --self-test"
+  }
+}

package/plugins/xr-dev/.claude-plugin/plugin.json

@@ -0,0 +1,37 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
+  "name": "xr-dev",
+  "displayName": "XR Dev",
+  "description": "Seven skills for the Meta Quest product lifecycle: platform and engine discovery, immersive design, native OpenXR, Kotlin Spatial and hybrid apps, WebXR/PWA, rendering experiments, tool and source discovery, Store submission, monetization, launch assets and post-launch operation. Agents receive stage-specific next actions, evidence gates and fallbacks when tools or devices are absent. Engine specialists remain separate; live requirements are verified against current Meta documentation.",
+  "version": "0.3.0",
+  "author": {
+    "name": "ssheleg",
+    "url": "https://x.com/sshlg93"
+  },
+  "homepage": "https://skills.sshlg.me/skills/xr-dev/",
+  "repository": "https://github.com/ssheleg/xr-dev",
+  "license": "MIT",
+  "keywords": [
+    "agent-skills",
+    "android-ndk",
+    "ar",
+    "bubblewrap",
+    "claude-code",
+    "cursor",
+    "horizon-os",
+    "kotlin",
+    "meta-quest",
+    "metavr",
+    "mruk",
+    "openxr",
+    "perfetto",
+    "pwa",
+    "quest",
+    "renderdoc",
+    "spatial-sdk",
+    "vr",
+    "vulkan",
+    "webxr",
+    "xr"
+  ]
+}