Build with AI agents
GlassKit ships its own agent skill — every scaffolded app comes with its agent pre-briefed on the platform contract (Claude Code, Cursor, Copilot, anything that reads AGENTS.md), plus llms.txt and an MCP server for the registry.
Most Display web apps will be built with an AI assistant in the loop. The failure mode is never "couldn't find the component" — it's procedural: an agent that assumes touch input, invents a dictation flow, or hand-writes a worse List. GlassKit ships the cure in three layers.
The skill (procedural knowledge)
Every npm create glasskit scaffold includes its agent skill — the new app
arrives with its agent already briefed:
| File | Read by |
|---|---|
AGENTS.md | the cross-agent contract — platform truth, focus rules, build conventions |
CLAUDE.md | Claude Code (imports AGENTS.md) |
.claude/skills/glasskit-ui/SKILL.md | Claude Code / Agent SDK — the full build procedure, loaded on demand |
.cursor/rules/glasskit.mdc | Cursor (always applied) |
.github/copilot-instructions.md | GitHub Copilot |
Existing project? One command, never overwrites:
npx @glasskit-ui/cli agentsThe reference (knowledge)
glasskit.app/ui/llms.txt — the
LLM-facing reference: platform facts, SDK API, conventions, and all 48
components with descriptions. Generated from the registry, so it can't
drift. Paste it into any model's context.
The tools (hands)
The MCP server exposes the registry to agents as tools — search components, read their source, get install commands:
npx @glasskit-ui/mcpWorks with Claude Code (claude mcp add glasskit -- npx @glasskit-ui/mcp),
Cursor, and any MCP client.
The skill encodes the same contracts the docs do — the platform wishlist honesty list, the patterns decision rules, and the API stability freeze — so human-written and agent-written GlassKit apps converge on the same shape.
Example apps
Complete multi-screen apps composed from the real components — drive them with your keyboard here, or scan the QR and run them on your glasses. Workout (Navigator + Timer + destructive Confirm) and Messages (threads + ComposeFlow replies).
Platform wishlist
APIs the Meta Ray-Ban Display doesn't expose to web apps yet — with GlassKit components already built and waiting for each one. The UI ships today; the day Meta exposes the API, it plugs in.