Launching today
GlassKit UI
AI-ready React UI for Meta's Ray-Ban Display glasses
24 followers
AI-ready React UI for Meta's Ray-Ban Display glasses
24 followers
Open-source (MIT) React components for Meta Ray-Ban Display web apps. 44 components + a D-pad focus engine for the 600x600 lens, and built for AI agents: a skill, an MCP server, and llms.txt so Claude/Cursor build it right. Vendor shadcn-style; own the source.
The copy-into-your-repo model makes sense here. Before editing a component heavily, Iād want to know the update path: do you re-run the CLI and merge a diff, or treat modified components as forked?
It's the shadcn model, so there are really two layers with different update stories.
The runtime is a versioned npm dep. The platform-critical stuff (the spatial focus engine, system-back navigation, the sensor hooks, GlassViewport) all lives in @glasskit-ui/react. That stays in your package.json and updates over semver like any other dependency. You never vendor or fork it, so you keep getting fixes for the gnarly Display-runtime behavior for free.
The components are yours. When you "glasskit add now-playing", the styled component source drops into your repo and you own it.