What problem does it solve? Building features for Meta smart glasses (Ray-Ban Meta, Oakley Meta, Ray-Ban Display) requires choosing between three distinct surfaces — the iOS Device Access Toolkit, the Android Device Access Toolkit, and Ray-Ban Display Web Apps — while keeping compile, mock, connected-device, physical-device, and release evidence strictly separate. This Skill acts as a technical lead that routes each request to the correct specialist pass and blocks unsupported claims such as unverified Gen 3 support or assumed cross-platform API parity. ## Core Features & Use Cases - Route planning and team orchestration: Selects the narrowest supported route (native DAT iOS, DAT Android, Web App, or phone fallback) and delegates to 23 local specialist roles with 32 upstream role handoffs defined in a validated team manifest. - Deterministic preflight tooling: Ships scripts for target-surface inspection, team preflight decisions, capability routing receipts, and a static fixture suite that exercises manifest validators, Web App checks, and Android preflight. - Evidence ledger discipline: Produces structured outputs including compatibility tables, privacy contracts, security/identity contracts, and routing receipts that keep source, build, physical, and release proof separate. - Use Case: When asked to "use the full Meta Wearables SDK for a Display feature on iOS and Android," the Skill runs the routing receipt, freezes the exact package/artifact revisions, assigns owner roles, and returns an implementation handoff with explicit to-verify items instead of inventing APIs. ## Quick Start Ask the agent to plan and route a Meta Wearables feature, for example: "Plan a Ray-Ban Display glance card feature with iOS DAT, Android DAT, and a phone fallback, and tell me what evidence is actually proven."
