meta-wearables-dat-integrationIntegrate or review the native Meta Wearables Device Access Toolkit (DAT) in an iOS (Swift, SPM) or Android (Kotlin, Gradle/Maven) companion app — package and artifact resolution, Info.plist or Manifest configuration, registration, permissions, URL/intent callbacks, device sessions, typed state and
meta-wearables-device-capabilitiesDesign, implement, or review what a native DAT app does with Meta smart glasses hardware — camera streams and photo capture, HFP microphone and A2DP audio routes, native DAT Display views and ButtonGroup input, D-pad/EMG/temple input and IMU/motion/location sensors, and the Bluetooth/Wi-Fi transport
meta-wearables-device-proofPlan and audit reproducible target preflight and evidence for Meta Wearables apps across source inspection, iOS/Android/Web App inventory, unit/build checks, DAT MockDevice, browser simulator, connected-device tests, and physical Ray-Ban/Oakley/Meta glasses. Use whenever a result could be mistaken f
meta-wearables-diagnosticsDiagnose and recover Meta Wearables DAT iOS/Android, native Display, and Display Web App failures, and resolve device and version compatibility — first failing state across registration, permissions, link, session, camera/audio/Display, transport, firmware, and companion, with a redacted diagnostic
meta-wearables-implementation-recipesTurn a selected Meta Wearables API row and vertical-slice playbook into source-aligned Swift, Kotlin/Java, or Ray-Ban Display Web App implementation scaffolding with explicit compile, privacy, lifecycle, fallback, and physical-device gates. Use when building or reviewing a concrete iOS DAT, Android
meta-wearables-knowledge-baseReference-only library for the meta-wearables-ops skills — source-pinned Meta Wearables DAT iOS/Android and Web Apps documents, the shared rules (evidence ladder, device labels, secrets), and the official source registry. Not a task skill. Use when another meta-wearables-ops skill links here or when
meta-wearables-route-plannerEntry point for any Meta Wearables app or feature. Picks the route (DAT iOS, DAT Android, native Display, Ray-Ban Display Web App, phone fallback, or blocked), designs the architecture (shared domain, adapters, state owner, fallback, test seams), and runs new-project intake. Use when starting a wear
meta-wearables-sdk-auditAudit Meta Wearables SDK coverage and resolve exact API surface — full-SDK and cross-platform parity audits across DAT iOS, DAT Android, native Display, and Web Apps; the iOS DAT API atlas (MWDAT modules, symbols, 0.9 migration); and the source-pinned surface manifest plus capability/evidence plan w
meta-wearables-trust-and-releaseOwn the trust and release boundary for Meta Wearables DAT iOS/Android, native Display, and Display Web Apps — on-device and data-flow claims, privacy and consent, privacy manifests and store review, app identity and attestation (MetaAppID, ClientToken, callbacks, package tokens), and Developer Cente
meta-wearables-web-appsBuild and review Meta Wearables Web Apps for the Ray-Ban Display with the official HTML/CSS/JavaScript route, 600×600 display contract, public HTTPS delivery, focus and D-pad/EMG input, performance limits, source-conflict handling, and separate simulator/physical-device evidence. Use when building o