meta-wearables-implementation-recipes

Generate source-aligned Swift, Kotlin, and Web App scaffolding for Meta Wearables DAT features.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Building features for Meta smart glasses requires navigating the Wearables Device Access Toolkit across iOS, Android, native Display, and Web App surfaces, where invented API symbols, missing compile gates, and unclear privacy boundaries cause broken implementations. This Skill converts a selected API row and vertical-slice playbook into validated, source-aligned implementation scaffolding with explicit compile, privacy, lifecycle, and physical-device gates. ## Core Features & Use Cases - Implementation Handoff Validation: Creates and validates a structured handoff packet (route, target tuple, API rows, evidence tasks, data contract, lifecycle) against the surface manifest, capability plan, and team manifest using a Python validator. - Source-Aligned Starters: Ships compile-tested or compile-gated starter adapters for iOS camera, iOS/Android Display, iOS/Android MockDevice fixtures, an Android Gradle target shell, and a dependency-free 600x600 Web App reducer. - Evidence-Gated Workflow: Enforces a verification ladder from source through build, mock/browser, connected, physical, and signed release, preventing mock or compile results from being claimed as hardware proof. - Use Case: After selecting the native iOS Display playbook, generate a validated handoff packet, adapt the Display starter against the pinned DAT 0.9.0 SPM products, and receive the exact next proof task and open gates. ## Quick Start Ask the assistant to turn the selected Meta Wearables playbook and API rows into an iOS or Android adapter scaffold with a validated implementation-handoff packet.

Frequently Asked Questions about meta-wearables-implementation-recipes

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

FAQPage Schema
How do I scaffold a Meta Wearables DAT camera feature on iOS or Android?

Select the camera playbook, create an implementation-handoff packet, and validate it with the bundled Python script. Then adapt the iOS or Android camera starter, which follows the DAT 0.9.0 consolidated Camera ownership path with explicit compile gates and camera-before-session teardown.

What is the implementation handoff packet and how is it validated?

It is a YAML packet capturing the route, target tuple, API rows, evidence tasks, owner roles, data contract, lifecycle, and tests. Run validate_implementation_handoff.py against the surface manifest, capability plan, and team manifest; unknown IDs, placeholders, or secret-like literals fail validation.

Does the Android target starter compile out of the box?

No. The starter pins AGP 8.11.1, Kotlin 2.2.21, SDK 36, and the mwdat 0.9.0 artifacts, but requires an Android SDK, Gradle, and authenticated GitHub Packages access. Copy it into a sibling project, supply credentials via environment or ignored local.properties, then run gradle :app:assembleDebug.

Can MockDevice tests prove physical glasses behavior?

No. MockDevice fixtures on iOS and Android establish deterministic state, permission, media, and captouch handling only. They cannot prove Bluetooth timing, camera optics, audio routing, Display legibility, firmware, thermal behavior, or Gen 2/Gen 3 compatibility; those require connected and physical evidence tasks.

What are the limitations of the Web App starter?

The dependency-free starter proves only bounded 600x600 reducer behavior for focus, stale input, network loss, host exit, and phone fallback via Node tests. The host toolkit contract, browser simulator, hosted HTTPS deployment, and physical Display run remain separate evidence gates.