meta-wearables-app-architecture

What problem does it solve? Building apps on Meta Wearables DAT often leads to platform SDK types leaking into UI and domain code, making the architecture fragile when glasses are absent, disconnected, permission-denied, or thermally limited. This Skill structures the product boundary before any DAT symbol is imported. ## Core Features & Use Cases - Layered boundary design: Separates shared domain/policy, platform adapters (Swift, Kotlin, Web App), surface presenters, and test fakes so DAT imports never reach views or domain models. - State machine and lifecycle modeling: Defines registration, permission, session, capability, thermal, and fallback states with session epochs and typed fallback instead of hidden retries. - Vertical-slice playbooks: Ships five playbooks (native Display card, camera-to-phone, audio-first, Web App, cross-surface) with proof ladders from reducer tests through physical-device evidence. - Use Case: When starting a new glasses companion app, use this Skill to produce a module boundary diagram, adapter interface map, data-flow classification, and a test-seam matrix before writing Swift or Kotlin code. ## Quick Start Use the meta-wearables-app-architecture skill to design the module boundaries and fallback state machine for a camera-to-phone Meta glasses feature.