Use case — Design system storage

A single source of truth for your design system.

Right now your design system lives in fragments — a stale DESIGN.md here, a screenshot pasted into a prompt there. Eyedropper stores one canonical, versioned system in the cloud and serves it to every AI agent, on every project, for every teammate.

Set up my design system

Extracted from your shipped code in one prompt.

Where your system lives today

A DESIGN.md in every repo

Each copy drifts the moment the brand shifts. Nobody remembers which one is current, so the newest repo gets the oldest rules.

Screenshots pasted into prompts

A screenshot carries one session. The next session — or the next teammate — starts from zero, and the agent guesses again.

Hex codes in Slack

The moment a second person with their own agent joins, there's no way to share design rules beyond messaging a file and hoping.

One canonical system, served live

Extracted from shipped code

Your agent reads the app you've already built and pushes the real system — colors, type, spacing, components, and usage rules — up to Eyedropper. No Figma library required.

extraction → 40 of 40 tokens · pushed

Versioned, with history

Every change is a version you can inspect and restore. The system evolves with your brand instead of forking into stale copies.

v12 → v13 · restore anytime

Served over MCP

Every agent on every project consults the same live system before generating anything visual — Claude Code, Cursor, any agent that speaks MCP.

npx eyedropper init

Change it once. Everything follows.

Update a color, a radius, a usage rule — every project picks it up on its next session. And your system is never trapped here: one click exports a clean DESIGN.md and standard design-tokens JSON, on any plan, anytime.

Set up my design system