Run any Skill in Manus with one click

passthrough-mr

Stars3

Forks0

UpdatedJune 5, 2026 at 13:04

Use when setting up or tuning Mixed Reality in Ankhora — enabling Meta Passthrough so the learner sees their real room with virtual content composited in, configuring underlay/overlay, depth/occlusion, or deciding MR-vs-VR for a scene. Triggers: passthrough, mixed reality, MR, see-through, OVRPassthroughLayer, composite, occlusion, depth, real room, see the real world, environment.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

LenySauzet

LenySauzet/Ankhora

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	passthrough-mr
description	Use when setting up or tuning Mixed Reality in Ankhora — enabling Meta Passthrough so the learner sees their real room with virtual content composited in, configuring underlay/overlay, depth/occlusion, or deciding MR-vs-VR for a scene. Triggers: passthrough, mixed reality, MR, see-through, OVRPassthroughLayer, composite, occlusion, depth, real room, see the real world, environment.

Passthrough / Mixed Reality (Meta)

Ankhora is MR training, not VR: the learner stands in their real workshop/kitchen and sees virtual ghost hands + annotations composited over the real world. That requires Passthrough, built on OVRPassthroughLayer and passthrough enabled in OVRManager.

Verify the API/config first via meta_get_config_information and context7/Meta docs — passthrough support flags and the OVRPassthroughLayer surface depend on the SDK version (com.meta.xr.sdk.all 201.0.0). Don't guess field names.

Setup order

meta_get_config_information — confirm Passthrough Support is enabled in the project config; check the camera rig's clear flags.
Add/enable an OVRPassthroughLayer (an underlay — virtual content renders on top of the real-world feed). Set the camera background to transparent (clear color alpha 0) so the real world shows through.
Manifest: passthrough capability via meta_update_android_manifest if the SDK version requires it; verify against the config.

Key decisions for Ankhora

Underlay vs overlay: annotations and ghost hands are virtual content over reality → underlay passthrough, content on top. Overlay only for deliberate "tint the world" effects.
Occlusion / depth: if virtual content must hide behind real objects (a tool occluding a ghost hand), you need the Depth API / scene mesh. This is costly on Quest — only add it if the masterclass genuinely needs occlusion; for the MVP, simple composited content without depth occlusion is usually enough. Decide explicitly.
Comfort & legibility: content read against a bright real room needs strong contrast and emissive (see xr-ui-design and urp-shadergraph). No full-screen passthrough tints that wash out content.

Verify

On device / Meta XR Simulator: the real world is visible, ghost hands + annotations composite correctly, no black background bleeding through. Mac Editor Play Mode cannot render passthrough — verify on device or simulator and say which.
Unity_SceneView_Capture2DScene for a static sanity check of layer setup.
Unity_ReadConsole: no passthrough/layer errors.

Out of scope

Scene understanding at scale, room-mesh-driven physics, dynamic relighting — V2. Keep MVR passthrough to "real room + composited content."

More from this repository

same repository

insights-report

LenySauzet/Ankhora

Use to generate Ankhora's project insights / progress report for an Epitech follow-up or any review — a dated, self-contained HTML file with charts (KPIs, velocity, contribution, board, quality, PRs-by-type, decisions & discoveries, feature-flow diagrams, what worked / didn't, improvement ideas), AND to derive a horizontal slideshow deck from it for live presentation. Both share Ankhora's branded "spatial control deck" design (dark visionOS/Meta-Spatial glass, anchor logo, Bricolage Grotesque display). Pulls from the repo docs/ADRs, git history (all branches), the PRs (CodeRabbit + Claude summaries) and the GitHub Project board. Triggers: "rapport d'insights", "rapport de suivi / follow-up", "progress report", "KPI report", "rapport pour la présentation", "génère le diaporama / la présentation / les slides", "slideshow / deck".

2026-06-263

git-commit

LenySauzet/Ankhora

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

2026-06-053

new-xr-interaction

LenySauzet/Ankhora

Use when adding or assembling an XR interaction in the Ankhora Quest 3 scene — a camera/hand rig, a grabbable, a poke/ray canvas, a teleport hotspot, or a spatial-anchor + annotation. Drives the Meta XR Building Blocks (meta_* tools) in the correct order, defines the scene's required-object contract, and verifies the result with a scene capture. Triggers: add XR rig, hand tracking rig, grabbable, interaction rig, poke canvas, ray canvas, teleport, spatial anchor, annotation, build the masterclass scene.

2026-06-053

record-replay-contract

LenySauzet/Ankhora

Use when defining, extending, or consuming Ankhora's core record/replay data model — the masterclass timeline of hand poses, head pose, events (annotation/anchor), and the audio track reference. The spine of the product; read this before touching capture or replay code. Triggers: record format, replay data, masterclass file, timeline, hand pose serialisation, data model, schema, frame format, what gets saved, serialize masterclass, DTO.

2026-06-053

spatial-anchors

LenySauzet/Ankhora

Use when persisting or restoring a position in the user's real space in Ankhora — placing, saving, loading, or erasing a Meta Spatial Anchor so an annotation or object stays put across a session. Triggers: spatial anchor, OVRSpatialAnchor, persist position, anchor an annotation, world-locked, save anchor, load anchor, erase anchor, anchor in real space, where did the user place it.

2026-06-053

unity-testability

LenySauzet/Ankhora

Use when deciding how to make Ankhora gameplay logic testable, isolating logic out of MonoBehaviour, or choosing between EditMode and PlayMode tests. Especially for the record/replay core (serialising hand poses, timeline stepping, annotation/anchor data) which should be plain C# and EditMode-tested. Triggers: testability, how to test this, write a test, unit test, EditMode, PlayMode, isolate logic, mockable, record replay logic, dependency injection in Unity.

2026-06-053

name	passthrough-mr
description	Use when setting up or tuning Mixed Reality in Ankhora — enabling Meta Passthrough so the learner sees their real room with virtual content composited in, configuring underlay/overlay, depth/occlusion, or deciding MR-vs-VR for a scene. Triggers: passthrough, mixed reality, MR, see-through, OVRPassthroughLayer, composite, occlusion, depth, real room, see the real world, environment.

Passthrough / Mixed Reality (Meta)

Verify the API/config first via meta_get_config_information and context7/Meta docs — passthrough support flags and the OVRPassthroughLayer surface depend on the SDK version (com.meta.xr.sdk.all 201.0.0). Don't guess field names.

Setup order

meta_get_config_information — confirm Passthrough Support is enabled in the project config; check the camera rig's clear flags.
Add/enable an OVRPassthroughLayer (an underlay — virtual content renders on top of the real-world feed). Set the camera background to transparent (clear color alpha 0) so the real world shows through.
Manifest: passthrough capability via meta_update_android_manifest if the SDK version requires it; verify against the config.

Key decisions for Ankhora

Underlay vs overlay: annotations and ghost hands are virtual content over reality → underlay passthrough, content on top. Overlay only for deliberate "tint the world" effects.
Occlusion / depth: if virtual content must hide behind real objects (a tool occluding a ghost hand), you need the Depth API / scene mesh. This is costly on Quest — only add it if the masterclass genuinely needs occlusion; for the MVP, simple composited content without depth occlusion is usually enough. Decide explicitly.
Comfort & legibility: content read against a bright real room needs strong contrast and emissive (see xr-ui-design and urp-shadergraph). No full-screen passthrough tints that wash out content.

Verify

On device / Meta XR Simulator: the real world is visible, ghost hands + annotations composite correctly, no black background bleeding through. Mac Editor Play Mode cannot render passthrough — verify on device or simulator and say which.
Unity_SceneView_Capture2DScene for a static sanity check of layer setup.
Unity_ReadConsole: no passthrough/layer errors.

Out of scope

Scene understanding at scale, room-mesh-driven physics, dynamic relighting — V2. Keep MVR passthrough to "real room + composited content."