Agent skills for building on the next generation of display wearables — Meta Ray-Ban Display, Snap Spectacles, and the platforms coming after them.
A library of Agent Skills that teach any coding agent — Claude Code, Cursor, Codex, Windsurf, anything that reads project rules — how to build apps for display-class smart glasses. Each skill is a graph: a Map of Content plus atomic concept nodes connected by wikilinks, scanned before they're read.
This repo opens with two providers — Meta and Snap — and grows. Stub folders exist for Xreal, Brilliant Labs, Mentra/AugmentOS, and Even Realities / Solos / Halliday with contribution guides for each.
npx skills add HKTITAN/thenextinterfaceThis uses the skills.sh CLI to install the skills into your detected agent. The CLI will prompt for scope (project vs. global) and method (symlink vs. copy).
GUIDELINES.md is the cross-vendor design reference for building interfaces on smart glasses. It distils principles from Meta, Snap, and general AR design literature into one canonical document — the bible. Both humans and agents reference it when designing for the medium. The provider-specific design skills (meta-display-design, snap-spectacles-design) apply its principles; this is the foundation.
The fastest way to set up any coding agent — Claude Code, Cursor, Windsurf, Codex, Aider, Cline, or anything that reads project rules — is to drop the block below into your agent's instructions / AGENTS.md / .cursorrules / system prompt.
You have access to "The Next Interface" — a library of agent skills for
building apps on display wearables (Meta Ray-Ban Display, Snap Spectacles,
and other glasses coming online). Use them whenever the user is choosing a
target device, wiring up gestures or voice or display, designing a HUD UX,
shipping a lens, or debugging a wearables-specific issue.
- Repo: https://github.com/HKTITAN/thenextinterface
- Skills root: https://github.com/HKTITAN/thenextinterface/tree/main/skills
- Install: npx skills add HKTITAN/thenextinterface
- Authoring rules: AGENTS.md at the repo root.
- Design bible: GUIDELINES.md at the repo root — the cross-vendor design
reference. Every design decision should be traceable to
a section of this document.
Each skill is a graph:
- `skills/<provider>/<skill>/SKILL.md` is a Map of Content — short
descriptions plus [[wikilinks]] to atomic concept nodes.
- `skills/<provider>/<skill>/references/<node>.md` are atomic concept files.
Each follows the same body contract: Concept → How <Vendor> provides it
→ The transferable pattern → Apply to your app.
- Cross-skill wikilinks like
`[[../../snap/snap-spectacles-design/references/fov-safe-zone]]` let you
traverse the whole library as one graph.
The two entry-point skills — `meta-wearables` and `snap-spectacles-build` —
each embed a "First, ask the user" block. Use them when the user has not
yet named a target device. They route to the specific skill once the user
answers.
Providers in v1:
- meta/ Meta Ray-Ban Display + Ray-Ban Meta + Oakley HSTN/Vanguard
- snap/ Snap Spectacles (5th gen) on Snap OS
- xreal/ STUB — Nebula SDK, DP-tethered display glasses
- brilliant/ STUB — Frame / Frame Glass, open-source MicroPython
- mentra/ STUB — AugmentOS, cross-vendor open OS
- even-realities/ STUB — G1, Solos, Halliday (minimal-display class)
Rules:
1. Before recommending anything, route through the relevant entry-point
skill's "First, ask the user" block if the target device is unknown.
2. Cite the node path you used (e.g.
`skills/snap/snap-spectacles-sik/references/hand-interactor.md`).
3. Prefer reading a specific `references/<node>.md` over the whole SKILL.md
when you know the area — cheaper on context, the graph is built for it.
4. Every claim about a vendor API should link to the canonical doc URL the
node cites. If the doc has moved, flag it — don't guess.
5. Follow the "Don't load for…" hints; off-target loading is the #1
failure mode.
| Skill | Use it when… |
|---|---|
meta-wearables |
The user is choosing between Meta devices, comparing Web Apps vs. Device Access Toolkit, or asks which Meta glasses their app can run on. |
meta-display-webapps |
Building HTML/CSS/JS apps for Meta Ray-Ban Display — viewport, focusable D-pad, Neural Band gesture mapping, additive-display rules, HTTPS deployment, QR pairing. |
meta-wearables-dat |
Extending an iOS or Android app with Meta Wearables Device Access Toolkit — Swift/Kotlin integration, session lifecycle, camera and mic streams, Mock Device Kit. |
meta-display-design |
Designing glanceable HUD UX for additive displays — contrast rules, micro-app archetypes, voice vs. gesture, audio cues, motion safety. |
| Skill | Use it when… |
|---|---|
snap-spectacles-build |
Building a Spectacles lens from scratch — Lens Studio 5, TypeScript programming model, scene structure, deployment, my-lenses portal. |
snap-spectacles-sik |
Wiring interactions — pinch, poke, gaze, two-handed manipulation, Interactable + InteractionManager event flow, custom interactors. |
snap-spectacles-sync |
Building Connected Lenses — Sync Kit's SessionController, SyncEntity, networked events, ownership, latency patterns. |
snap-spectacles-ai |
Adding AI features — SnapML on-device, Remote Service Gateway, ASR voice, Snap Cloud (Supabase), depth-cached vision. |
snap-spectacles-navigation |
Location and navigation — Custom Locations, Places API, Navigation Kit, indoor vs. outdoor patterns, anchor persistence. |
snap-spectacles-mobile-kit |
Bridging a phone or external device — BLE patterns, Spectacles Mobile Kit, sensor passthrough, Arduino/game controller integration. |
snap-spectacles-design |
Designing and shipping a polished lens — FOV safe zone, head/body/world-lock, performance budgets, lens-approval checklist. |
| Provider | Status | What goes here |
|---|---|---|
xreal |
Stub | Xreal Nebula SDK skills for Air, One, Beam Pro display glasses. |
brilliant |
Stub | Brilliant Labs Frame and Frame Glass — MicroPython-based open-source glasses. |
mentra |
Stub | AugmentOS — open-source operating system for smart glasses across vendors. |
even-realities |
Stub | Minimal-display glasses — Even Realities G1, Solos AirGo, Halliday. |
Each stub provider has a README.md describing what skills should eventually exist there and how to contribute one. See AGENTS.md for the authoring rules every new skill follows.
Each skill is a graph, not a single file. The pattern (per Akshay Pachaar's "Skill Graphs > SKILL.md", shaped by Perplexity's skill-engineering write-up and Garry Tan's gstack):
SKILL.mdis a Map of Content — short descriptions of every node, plus[[wikilinks]]. It also carries the trigger description (the routing trigger, ≤350 chars), a## When to loadblock with positive triggers and "Don't load for" lines, a## Decide firstblock of forcing questions, a## Verifychecklist, and a## Smoke testfor eval.references/*.mdare atomic concept files — one complete thought each, with YAML frontmatter (name,summary,metadata.internal: true) so the skills.sh CLI doesn't surface them as separate skills. Each follows a 4-section body contract: Concept → How <Vendor> provides it → The transferable pattern → Apply to your app.- Cross-skill wikilinks span providers:
[[../../snap/snap-spectacles-design/references/fov-safe-zone]]from inside a Meta skill is valid.
The two entry-point skills — meta-wearables and snap-spectacles-build — open with a ## First, ask the user block. The agent reads the block, asks the user the listed questions (which device, hardware vs. blind, distribution timeline), and routes to the right downstream skill based on the answers. This is the Perplexity "load when…" pattern combined with gstack's confusion protocol — refuse to guess on architectural decisions; force the answer into the open.
thenextinterface/
├── AGENTS.md
├── README.md
├── LICENSE
├── .markdownlint.jsonc
├── .github/workflows/validate.yml
├── scripts/validate.py
├── .agents/
│ ├── README.md
│ ├── shared/
│ │ ├── skill-graph.md
│ │ ├── frontmatter.md
│ │ ├── voice.md
│ │ ├── verification.md
│ │ ├── onboarding-pattern.md
│ │ └── adding-a-provider.md
│ ├── claude-code.md
│ ├── codex.md
│ └── cursor.md
└── skills/
├── meta/
│ ├── meta-wearables/
│ ├── meta-display-webapps/
│ ├── meta-wearables-dat/
│ └── meta-display-design/
├── snap/
│ ├── snap-spectacles-build/
│ ├── snap-spectacles-sik/
│ ├── snap-spectacles-sync/
│ ├── snap-spectacles-ai/
│ ├── snap-spectacles-navigation/
│ ├── snap-spectacles-mobile-kit/
│ └── snap-spectacles-design/
├── xreal/ (stub)
├── brilliant/ (stub)
├── mentra/ (stub)
└── even-realities/ (stub)
Meta:
- Build for Display Glasses announcement — https://developers.meta.com/blog/build-for-display-glasses/
- Meta Wearables developer hub — https://wearables.developer.meta.com
- Device Access Toolkit docs — https://wearables.developer.meta.com/docs/develop/dat
- Web Apps docs — https://wearables.developer.meta.com/docs/develop/webapps
- iOS DAT GitHub — https://github.com/facebook/meta-wearables-dat-ios
- Android DAT GitHub — https://github.com/facebook/meta-wearables-dat-android
- Web Apps Starter Kit — https://github.com/facebookincubator/meta-wearables-webapp
Snap:
- Spectacles developer hub — https://developers.snap.com/spectacles
- Spectacles Interaction Kit — https://developers.snap.com/spectacles/spectacles-frameworks/spectacles-interaction-kit/get-started
- Spectacles Sync Kit — https://developers.snap.com/spectacles/spectacles-frameworks/spectacles-sync-kit/overview
- Canonical sample projects — https://github.com/specs-devs/samples
- Lens Studio — https://ar.snap.com/spectacles
GUIDELINES.md— the design bible for display wearables- skills.sh — the CLI and registry
- Agent Skills spec
- agents.md — the AGENTS.md format
- Skill-graph idea: @akshay_pachaar
- Skill engineering: research.perplexity.ai
- Sprint-stage workflow: garrytan/gstack
- Reference repo this one borrows conventions from: HKTITAN/duolingo
MIT