meta-wearables-route-planner
Entry 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 wearable app or feature, when a request names Ray-Ban Meta, Oakley Meta, Meta Glasses, Display, Gen 2, Gen 3, or the Meta Wearables SDK, or when deciding how iOS, Android, Display, and Web App code share behavior.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- meta-wearables-route-planner
- description
- Entry 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 wearable app or feature, when a request names Ray-Ban Meta, Oakley Meta, Meta Glasses, Display, Gen 2, Gen 3, or the Meta Wearables SDK, or when deciding how iOS, Android, Display, and Web App code share behavior.
- allowed-tools
- Read, Grep, Glob
- last_verified
- 1787356800000
02 资源文件 4
- 参考文档references/architecture-contract.md7.1 KB
- 参考文档references/project-bootstrap-packet.md4.9 KB
- 参考文档references/route-details.md4.6 KB
- 参考文档references/vertical-slice-playbooks.md12.6 KB
03 SKILL.md 正文
Meta Wearables route planner
Overview
Turn a wearable idea into a verified route and an architecture before package imports, UI, permissions, or marketing copy harden around an assumption. This skill plans; the lane skills build. Hand off once the route is chosen:
| Lane | Skill |
|---|---|
| "Full SDK", parity, API atlas, surface manifest | meta-wearables-sdk-audit |
| DAT iOS/Android setup, registration, Android API atlas | meta-wearables-dat-integration |
| Camera, audio, native Display, input, sensors, transport | meta-wearables-device-capabilities |
| Ray-Ban Display Web Apps | meta-wearables-web-apps |
| Swift, Kotlin, Web App scaffolding | meta-wearables-implementation-recipes |
| Failures, readiness, compatibility | meta-wearables-diagnostics |
| On-device claims, privacy, attestation, Developer Center, release | meta-wearables-trust-and-release |
| Connected, physical, signed proof | meta-wearables-device-proof |
Apply the shared rules — evidence ladder, device labels, secrets, claims.
Read before acting
- Inspect the real workspace: Xcode project, Gradle build, hosted Web App, min SDK, package graph, permissions, and existing device integrations. If none exists, this is a bootstrap.
- Read platform and route selection, the device models and capability matrix, application architecture and platform boundaries, and the Meta source registry.
- Resolve user wording through the
terminology_contractin the surface manifest before picking a route. Keep ambiguous terms ambiguous. - Route details maps request wording to the knowledge-base page to read and lists assumptions to reject.
- Refresh the official DAT iOS and DAT Android repositories before relying on a version-sensitive symbol.
Route map
| User outcome | Route | First gate |
|---|---|---|
| iOS app uses glasses capabilities | native DAT iOS | package/API and registration |
| Android app uses glasses capabilities | native DAT Android | Gradle/API and registration |
| glanceable native surface from the phone app | DAT Display | supportsDisplay() and physical model |
| HTML/CSS/JS on Ray-Ban Display | Web App | public HTTPS URL, 600×600, focus/input |
| wearer input, motion, orientation, location | Display, Web App, or phone | source/permission gate plus physical task |
| setup, consent, unavailable, unsupported | phone-first fallback | useful phone flow without wearable |
| "Gen 3" or unnamed future model | blocked / to-verify |
device type, firmware, capability |
Native DAT and Web Apps can coexist in one product but stay separate routes.
Workflow
- Intake. Rewrite the request as an outcome (capture, show, notify, navigate, control, configure). Record surface, fallback, capabilities, device wording, processing location, evidence level, and worst-case failure.
- Pick the route from the map. Name rejected alternatives. Resolve "regular SDK" and "Gen 3" or return them blocked; never branch into every lane.
- Draw the boundaries with the architecture contract:
shared domain/policy, one wearable coordinator that reduces SDK events into
state, separate iOS, Android, Display, and Web App adapters, presenters, and
test fakes. DAT imports,
Flow/AsyncSequence,DatResult, and Web APIs stay inside adapters. - Model state before effects: registration, permission, device selection, session, capability, transport, thermal, cancellation, and fallback. Give each session an owner, an epoch, and a stop path so stale frames or Display actions cannot cross sessions. Fallback is typed state, not a retry spinner.
- Label the data path of every frame, sample, transcript, sensor value, Display payload, and log as glasses-native, phone-local, remote, mixed, or unknown.
- Pick one vertical slice from the playbooks: native Display, camera-to-phone, audio-first, Web App, or shared outcome. Carry its manifest row IDs, state machine, fallback, and proof ladder.
- No target yet? Fill the project bootstrap packet in a new sibling folder — never inside this skills repository — and pick the first slice.
- Hand off each lane to its owning skill with sources, versions, open gates, and the next proof task. Stop unless the user asked for the build.
Fast path
For one feature: route, four boxes (domain, adapter, presenter, fake), one playbook, one adapter method and typed fallback before any parity work.
Required output
- Route, rejected alternatives, and the terminology status of "Gen 3" and "regular SDK" from the manifest.
- Exact SDK repository, tag or commit, package/artifact, and device/model/capability table.
- Module boundary diagram, ownership table, and shared state machine with
platform adapter interfaces; symbols marked
source,compile, orto-verify. - Data-flow, privacy, thermal, lifecycle, and fallback contract.
- Selected vertical slice with manifest and evidence row IDs.
- Bootstrap packet with sibling path, when no target exists.
- Test seams (reducer, fake, MockDevice, browser, connected, physical) and the firmware/companion/channel/signing gates.
- Lane handoffs and the next evidence task.
Hard boundaries
- Never put DAT imports, Meta AI registration, or Web App browser APIs in a SwiftUI/Compose view or the shared domain model.
- Never treat one common interface as parity; return per-platform
unsupported or
to-verifystates where platforms differ. - Never call a phone-local fallback glasses-native, or a Web App a native DAT module.
- Never hide a camera, audio, Display, sensor, or remote failure behind an unbounded retry or a generic loading state.
- Plan only. Do not create accounts, request credentials, deploy, or contact testers without an explicit request.
04 同仓库更多 Skills
no-description
暂无简介
good-skill
Fixture skill that satisfies every rule.
broken-link
Links to a reference file that does not exist.
Bad_Name
Name violates the kebab-case rule and does not match the directory.
skill-authoring
Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.
weigh-bags
Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts/reconcile.py.