菜单
Load when the user is building location-aware AR on Snap Spectacles — Custom Locations for site-specific experiences, Places API for POI data, indoor / outdoor navigation, persistent spatial anchors, or asks "how do I make AR show up in this specific real place." Don't load for general lens basics — use snap-spectacles-build.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Load when the user is designing UX for Meta Ray-Ban Display — glanceable HUD patterns, micro-app archetypes (transit, cooking, lists), additive-display color rules, voice vs gesture choice, audio cues, motion safety. Don't load for technical Web App wiring — that's meta-display-webapps.
Load when the user is polishing a Snap Spectacles lens for shipping — FOV / safe zone, head vs body vs world lock, comfort and motion-sickness rules, performance and thermal budgets, lens publishing and review. Don't load for early build mechanics — use snap-spectacles-build.
Load when the user is bridging a phone or external BLE device to a Spectacles lens — sending phone sensor data into a lens, building a companion app, integrating Arduino / game controllers, or asks "how do I pair my own peripheral with Spectacles." Don't load for general Lens Studio basics — use snap-spectacles-build.
Load when the user is wiring pinch, poke, gaze, or two-handed manipulation on Snap Spectacles — building AR buttons, sliders, draggable objects, scrollable lists, custom interactors, or asks "why isn't my Interactable firing." Don't load for general Lens Studio scene setup — use snap-spectacles-build.
Load when the user is building an HTML/CSS/JS Web App for Meta Ray-Ban Display — choosing a viewport, wiring Neural Band and Cap Touch input, designing for the additive display, handling motion sensors or geolocation, or deploying over HTTPS so MRBD can load it. Don't load for non-MRBD Meta devices — those use the DAT path; route to meta-wearables-dat.
Load when the user is integrating Meta's Wearables Device Access Toolkit into an iOS or Android app to receive camera, microphone, or sensor streams from Ray-Ban Meta or Oakley glasses — wiring registration, permissions, streaming, the Mock Device Kit, or solving "the glasses don't appear in my device list." Don't load for MRBD Web Apps — that's meta-display-webapps.
| name | snap-spectacles-navigation |
| description | Load when the user is building location-aware AR on Snap Spectacles — Custom Locations for site-specific experiences, Places API for POI data, indoor / outdoor navigation, persistent spatial anchors, or asks "how do I make AR show up in this specific real place." Don't load for general lens basics — use snap-spectacles-build. |
| license | MIT |
| metadata | {"author":"HKTITAN","version":"1.0.0","graph":true,"depends":["snap-spectacles-build"]} |
Location-aware AR on Spectacles spans three concerns: positioning the user in the real world (GPS + visual tracking fusion), placing content at specific real-world locations (Custom Locations + Places API), and helping the user move between them (route planning, navigation UI). Each is its own discipline.
Triggers:
Don't load for:
The architecture decisions before code:
Before claiming a navigation-enabled lens is shippable:
If this skill loaded correctly, the agent should answer:
