Run any Skill in Manus with one click

world-space-annotations

Stars3

Forks0

UpdatedJune 5, 2026 at 13:04

Use when building Ankhora's in-MR annotation panels — a world-space text/label placed in real space (bound to a spatial anchor), readable and pokeable by the learner. Triggers: annotation, label, text panel, world-space canvas, callout, note in space, TextMeshPro in VR, poke panel, info bubble, step instruction panel.

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	world-space-annotations
description	Use when building Ankhora's in-MR annotation panels — a world-space text/label placed in real space (bound to a spatial anchor), readable and pokeable by the learner. Triggers: annotation, label, text panel, world-space canvas, callout, note in space, TextMeshPro in VR, poke panel, info bubble, step instruction panel.

World-space annotations

An annotation is Ankhora's atomic teaching unit: a short piece of text/marker placed in the real room (via a spatial anchor) that the learner reads and can interact with. This skill is the recipe for one; it sits on top of spatial-anchors, new-xr-interaction, and the xr-ui-design design language.

Anatomy of an annotation

A world-space Canvas (not screen-space) holding TextMeshPro text (TMP is sharp at distance; default UI text is not). Size it for arm's-reach-to-2 m legibility — see xr-ui-design.
Anchored in space: parent the annotation under an OVRSpatialAnchor (see spatial-anchors) so it stays on the real object as the learner moves. Store its annotationId + anchorId in the record/replay data (record-replay-contract).
Interaction (optional): make it pokeable with meta_add_canvas_interaction_poke (near, in-reach) or ray for far panels — go through Meta's Interaction SDK, never custom raycasts (Horizon Store requirement; see horizon-store-compliance).

Behaviour choices (decide per annotation)

World-locked vs billboard: instructions tied to a physical spot stay world-locked; a floating hint may billboard to face the learner. Default to world-locked for "this part here".
Legibility against passthrough: the real room is the background — use a solid/contrasting panel backing and emissive text so it reads over a bright kitchen/workshop (see urp-shadergraph).
Reveal timing: annotations appear/disappear as timeline events during replay (AnnotationShown / AnnotationHidden in the contract), not all at once.

Workflow over MCP

Build the canvas + TMP via Unity_ManageGameObject / Unity_ManageAsset; add poke interaction via meta_add_canvas_interaction_poke (call meta_get_config_information first).
Keep annotation data (id, text, anchor binding, show/hide times) in the contract DTO; the MonoBehaviour just renders it.

Verify

Unity_SceneView_Capture2DScene: panel is legible, correctly placed, faces sanely.
On device/simulator: poke works, text stays anchored as you move, readable over passthrough.
Unity_ReadConsole: clean.

Out of scope

Rich media annotations (video/3D widgets), authoring UI for end-users, localisation — V2. MVP = one short text annotation, anchored, optionally pokeable.

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

passthrough-mr

LenySauzet/Ankhora

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.

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

name	world-space-annotations
description	Use when building Ankhora's in-MR annotation panels — a world-space text/label placed in real space (bound to a spatial anchor), readable and pokeable by the learner. Triggers: annotation, label, text panel, world-space canvas, callout, note in space, TextMeshPro in VR, poke panel, info bubble, step instruction panel.

World-space annotations

Anatomy of an annotation

A world-space Canvas (not screen-space) holding TextMeshPro text (TMP is sharp at distance; default UI text is not). Size it for arm's-reach-to-2 m legibility — see xr-ui-design.
Anchored in space: parent the annotation under an OVRSpatialAnchor (see spatial-anchors) so it stays on the real object as the learner moves. Store its annotationId + anchorId in the record/replay data (record-replay-contract).
Interaction (optional): make it pokeable with meta_add_canvas_interaction_poke (near, in-reach) or ray for far panels — go through Meta's Interaction SDK, never custom raycasts (Horizon Store requirement; see horizon-store-compliance).

Behaviour choices (decide per annotation)

World-locked vs billboard: instructions tied to a physical spot stay world-locked; a floating hint may billboard to face the learner. Default to world-locked for "this part here".
Legibility against passthrough: the real room is the background — use a solid/contrasting panel backing and emissive text so it reads over a bright kitchen/workshop (see urp-shadergraph).
Reveal timing: annotations appear/disappear as timeline events during replay (AnnotationShown / AnnotationHidden in the contract), not all at once.

Workflow over MCP

Build the canvas + TMP via Unity_ManageGameObject / Unity_ManageAsset; add poke interaction via meta_add_canvas_interaction_poke (call meta_get_config_information first).
Keep annotation data (id, text, anchor binding, show/hide times) in the contract DTO; the MonoBehaviour just renders it.

Verify

Unity_SceneView_Capture2DScene: panel is legible, correctly placed, faces sanely.
On device/simulator: poke works, text stays anchored as you move, readable over passthrough.
Unity_ReadConsole: clean.

Out of scope

Rich media annotations (video/3D widgets), authoring UI for end-users, localisation — V2. MVP = one short text annotation, anchored, optionally pokeable.