菜单
visionOS game engine patterns and tradeoffs. Use when choosing between Unity PolySpatial, Unreal Engine, Godot, or native Metal for visionOS development — provides engine capabilities, rendering paths, simulator support, and integration patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | visionos-game-engines |
| description | visionOS game engine patterns and tradeoffs. Use when choosing between Unity PolySpatial, Unreal Engine, Godot, or native Metal for visionOS development — provides engine capabilities, rendering paths, simulator support, and integration patterns. |
Path 1 — RealityKit / Shared Space:
Path 2 — CompositorServices / Full Space:
LayerRendererUse CompositorLayer (not MTKView) as SwiftUI scene type for Path 2.
| Feature | Unity PolySpatial | Unreal 5.5+ | Godot (pending) | Native RealityKit |
|---|---|---|---|---|
| Shared Space | Yes | No | Yes (windowed) | Yes |
| Simulator | Yes | No (device only) | Likely | Yes |
| Custom shaders | No (MaterialX only) | Yes | Yes | Metal only |
| Hand tracking | Yes (XR Hands) | Yes (ARKit) | Yes (ARKit) | Yes (ARKit) |
| Passthrough (visionOS 2.0+) | Yes | Yes (UE 5.5+) | Pending | Yes |
| Embed in native app | Partial (separate SwiftUI windows) | No documented path | Unknown | N/A (it IS native) |
| License cost | Pro required | Free | Free (MIT) | Free |
Min versions: Unity 6 for 2.x packages; Unity 2022.3.18f1 for 1.x packages. Apple Silicon Mac required.
App modes (Project Settings > XR Plug-in Manager > Apple visionOS > App Mode):
Mixed Reality - Volume or Immersive Space → RealityKit renderingVirtual Reality - Fully Immersive Space → Metal/CompositorServices renderingHybrid (2.x only) → runtime switch between the twoSwiftUI interop pattern:
*InjectedScene.swift auto-merge into the app's top-level AppDllImportWhat doesn't work in PolySpatial (RealityKit) mode:
Versions: 5.4+ experimental (Full Immersion), 5.5+ adds Mixed Immersion (visionOS 2.0 required)
Key constraints:
Status (early 2026): Apple contributing 3-stage PR to Godot master branch. Stage 1 (windowed) merged. Stages 2-3 (Swift lifecycle, VR plugin) in progress. Not in binary releases yet — compile from source.
Community alternative: GodotVision (godot.vision) wraps Godot in RealityKit, already functional.
Mix native RealityKit chrome with game engine 3D content:
ZStack {
MetalGameView() // bottom: game engine renders to texture
RealityView { ... } // top: RealityKit 3D frame/chrome
}
@State variables drive dynamic frame changes (level transitions, etc.).
Unity's formal Hybrid Mode (2.x) manages this programmatically — performance overhead scales with scene complexity.
// Scene type for immersive Metal app
ImmersiveSpace {
CompositorLayer(configuration: MyConfig()) { layerRenderer in
MyRenderer(layerRenderer: layerRenderer).run()
}
}
// Render loop pattern
func run() {
while true {
guard let frame = layerRenderer.queryNextFrame() else { return }
frame.startSubmission()
// encode Metal commands for left+right eye
// use .layered layout + vertex amplification for stereo
frame.endSubmission()
}
}
Key notes:
.layered texture layout + Metal vertex amplification for single-pass stereoHandAnchor, WorldAnchor) separate from CompositorServicesOnly Unity and native RealityKit work in the Simulator. Everything targeting CompositorServices in full immersion can technically run in Simulator, but Unreal's toolchain doesn't support it.
Full expertise: /Users/quartershots/.claude/research/visionos-game-engines/expertise.md
Design consultation: understands your product, researches competitors, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview pages. Creates DESIGN.md as your project's design source of truth. Use when asked to "design my app", "create a design system", "pick fonts and colors", "design consultation", or "make it look good". For existing sites, use /plan-design-review to infer the system instead.
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update docs", "sync documentation", "document what shipped", "update the readme after shipping", or "post-release docs".
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review my plan", "eng review", "check my architecture", "review before I build", or "sanity check this plan".
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review my code", "review this PR", "check before merge", "pre-landing review", or "look at my diff".
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship it", "ship this branch", "merge and deploy", "create a PR", "land this", or "push to production".
Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence.