| 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"]} |
Spectacles Navigation โ Location AR + Custom Locations
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.
When to load
Triggers:
- "Spectacles navigation"
- "AR at a specific location"
- "Custom Locations Snap"
- "Places API in a lens"
- "Indoor / outdoor navigation"
- "Persistent spatial anchors"
- "Outdoor AR walking directions"
Don't load for:
- General Lens Studio basics โ [[../snap-spectacles-build/SKILL]].
- Multiplayer location experiences โ combine with [[../snap-spectacles-sync/SKILL]].
- Phone-companion location features โ see [[../snap-spectacles-mobile-kit/SKILL]] for phone-side GPS.
Decide first
The architecture decisions before code:
- Scope of "location." A specific room, a building, a city block, the whole world? Different scopes use different tools โ Custom Locations for site-specific, Places API for general POIs, GPS-fused for wide-area.
- Tracking model. GPS only (loose), visual + GPS (tight), or pre-mapped (most accurate). See [[references/gps-fusion]].
- Persistence. Does an anchor survive across sessions? Across users? See [[references/anchor-persistence]].
- Indoor vs outdoor. GPS doesn't work indoors; visual tracking varies. See [[references/indoor-vs-outdoor]].
Map of content
Foundations
- [[references/location-ar]] โ what "location AR" actually means on Spectacles.
- [[references/indoor-vs-outdoor]] โ what changes between the two contexts.
- [[references/navigation-kit-overview]] โ Snap's Navigation Kit at a glance.
Site-specific AR
- [[references/custom-locations]] โ Custom Locations API for mapping real spaces.
- [[references/anchor-persistence]] โ anchors that survive across sessions / users.
- [[references/large-area-mapping]] โ covering a building, a block, a campus.
Wayfinding
- [[references/places-api]] โ Places API for POIs.
- [[references/route-planning]] โ computing a path between points.
- [[references/map-component]] โ rendering a map / mini-map in the lens.
Positioning
- [[references/gps-fusion]] โ GPS + visual tracking; when each is the source of truth.
Verify
Before claiming a navigation-enabled lens is shippable:
Smoke test
If this skill loaded correctly, the agent should answer:
- The user wants AR at a specific museum exhibit. Which API? (Expected: Custom Locations โ pre-map the space, anchor content; cites [[references/custom-locations]].)
- The user wants AR labels on every coffee shop in a city. Which API? (Expected: Places API + GPS; cites [[references/places-api]] and [[references/gps-fusion]].)
- Why does outdoor navigation work but indoor often fails? (Expected: GPS is unavailable / unreliable indoors; visual tracking has to do all the work; cites [[references/indoor-vs-outdoor]].)
Sibling skills
- [[../snap-spectacles-build/SKILL]] โ Lens Studio basics.
- [[../snap-spectacles-sync/SKILL]] โ for shared / multiplayer location experiences.
- [[../snap-spectacles-mobile-kit/SKILL]] โ phone-side bridging for additional GPS / map UI.
Sources
