What problem does it solve? Building UI for Meta smart glasses is easy to get wrong: developers often shrink a phone screen onto the Display, assume capability from a product name, or skip teardown and fallback behavior. This Skill provides a structured workflow for designing native Meta DAT Display surfaces that are glanceable, capability-gated, and recoverable. ## Core Features & Use Cases - Capability-gated Display design: Query runtime support via APIs like DeviceType.supportsDisplay() instead of inferring from product names, and define a compact Display state machine (hidden, presenting, focused, dismissed, timedOut, disconnected, unsupported). - Input and interaction contract: Model ButtonGroup/action handling, focus, selection, dismiss, timeout, and accidental input, with high-contrast glanceable content and a phone fallback for every glasses action. - Teardown and evidence: Clear the Display on completion, cancellation, or disconnect, and produce mock/simulator fixtures plus a physical Ray-Ban Display test script with expected observations. - Use Case: When adding a native glasses UI to an iOS app using the Meta Wearables Device Access Toolkit, use this Skill to define the capability gate, state machine, input handling, phone handoff, and physical-device test plan before writing layout code. ## Quick Start Use the meta-dat-display skill to design a native Display surface for my Meta glasses feature, including the capability gate, state machine, input handling, and physical test plan.
