thenextinterface

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 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.

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.

Load when the user is choosing between Meta wearables (Ray-Ban Display vs Ray-Ban Meta vs Oakley HSTN/Vanguard), comparing build paths (Web Apps vs Device Access Toolkit), or asks "which Meta glasses can my app run on" or "what can I actually build on each Meta wearable." Don't load for already-decided builds — route to the specific path skill.

Load when the user is adding AI to a Spectacles lens — SnapML on-device models, voice ASR, Remote Service Gateway for LLMs and TTS, depth-cached vision, Snap Cloud as backend, or asks "how do I run a vision model on Spectacles." Don't load for general Lens Studio basics — use snap-spectacles-build.

Load when the user is starting a Snap Spectacles lens from scratch — installing Lens Studio, creating a project, writing the TypeScript scripting model, deploying to Spectacles, distributing through My Lenses, or asks "how do I build my first lens." Don't load for already-deep work on interactions, multiplayer, AI, or design — those have dedicated skills.

Load when the user is building multiplayer / Connected Lenses on Snap Spectacles — Sync Kit, SessionController, SyncEntity, networked prefabs, host migration, latency-tolerant UX, or asks "how do users share this lens." Don't load for single-user lenses — use snap-spectacles-build.