meta-dat-api-atlas

Maps the Meta Wearables DAT iOS API surface, migrations, and tooling against pinned source revisions.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/shotcowboystyle/meta-wearables-ops-plugin --skill meta-dat-api-atlas-shotcowboystyle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-dat-api-atlas
Source: https://github.com/shotcowboystyle/meta-wearables-ops-plugin/tree/main/.agent/skills/meta-dat-api-atlas
Command: npx skills add https://github.com/shotcowboystyle/meta-wearables-ops-plugin --skill meta-dat-api-atlas-shotcowboystyle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Version-sensitive Meta Wearables DAT work often fails because developers invent module imports, trust stale documentation, or claim SDK support without verifying the actual package. This Skill pins the exact DAT iOS release, maps confirmed versus unverified API symbols, and prevents unsupported claims about camera, audio, Display, and device compatibility. ## Core Features & Use Cases - Source-pinned API mapping: Freezes repository commits, changelog releases, and API reference URLs, then maps public module names to actual package products with confirmed or to-verify status. - Lifecycle route tracing: Traces the full flow from Wearables.configure() through registration, permissions, sessions, camera, Display, audio, and teardown with migration traps flagged. - Boundary enforcement: Separates native DAT from Web Apps, mock/simulator results from physical device proof, and refuses to map Gen 3 devices without official evidence. - Use Case: When asked to build an iOS app streaming glasses camera frames with Display support, use this Skill to pin the DAT 0.9 release, verify the addCamera signature, gate Display on supportsDisplay(), and route microphone capture through documented HFP behavior. ## Quick Start Ask the agent to map the exact DAT iOS modules, migration changes, and device proof gates needed for your Meta glasses feature before writing any integration code.

Frequently Asked Questions about meta-dat-api-atlas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify which Meta DAT iOS modules actually exist before integrating?

Pin the exact DAT iOS release or commit, then map public module names to the package products exposed by your target. Mark any machine-index-only names as to-verify until confirmed against the generated API of the selected release.

What changed in the Meta Wearables DAT 0.9 migration?

The 0.9 migration details come from the official DAT iOS changelog and API reference pinned to a specific release. The Skill traces lifecycle routes and flags versioned signature gates such as addCamera rather than relying on stale prose.

Can I use MockDevice tests as proof that glasses features work?

No. MockDeviceKit and its test server support deterministic UI tests but explicitly exclude physical camera, audio, and display proof. Physical-device evidence on named hardware is required for release claims.

Does the DAT SDK support Gen 3 Meta glasses?

Gen 3 must remain to-verify unless a current official device mapping and named-device evidence exist. Never alias Gen 3 to .metaGlasses, .rayBanMeta, or Display based on product announcements alone.

What is the difference between native DAT and Meta Wearables Web Apps?

Native DAT and Web Apps are distinct product journeys with different runtimes. Web Apps use a DOM/hosted URL route, and features like text composition, offline, and extended gestures stay source-conflicted until target proof closes the gap.