What problem does it solve? Teams building for Ray-Ban Meta, Oakley Meta, or Meta Glasses often commit to the wrong platform surface before verifying what the SDK and device actually support. This Skill turns a wearable product idea into a verified platform route before package imports, UI work, permissions, or marketing copy harden around an unproven assumption. ## Core Features & Use Cases - Route mapping: Maps a user outcome to native DAT iOS, native DAT Android, DAT Display, Ray-Ban Display Web Apps, phone fallback, or a blocked/to-verify status with explicit first gates. - Evidence-based compatibility labels: Classifies every capability as Documented, Build-proven, Mock-proven, Connected-device proven, Physical Display proven, or To verify. - Ambiguity resolution: Resolves vague wording like "Gen 3" or "regular SDK" against official Meta sources and the surface manifest terminology contract instead of inventing SDK symbols. - Use Case: A product team asks for "camera capture on Gen 3 glasses." The Skill rewrites this as an outcome, checks the device-generation matrix and DAT changelogs, and returns either a proven native DAT route with device/firmware evidence requirements or a blocked route with the exact open questions. ## Quick Start Ask the assistant to plan the platform route for a Meta glasses feature, for example: "Plan the correct Meta Wearables route for a glanceable notification experience on Ray-Ban Display."
