Token-first design
All styles flow through semantic tokens. Edit Primary once and every component restyles — across designers, code, and AI.
See the token model →--primary-*
--destructive-*
Edit design tokens visually. Your running app updates live through HMR. Claude Code modifies components through MCP.
The loop
All styles flow through semantic tokens. Edit Primary once and every component restyles — across designers, code, and AI.
See the token model →--primary-*
--destructive-*
Cmd-click any element in your running app. See its computed styles, edit them inline, and watch the iframe restyle in the same frame.
Read about the bridge →Saddle exposes structured component data over MCP, plus a per-variant component.md and a project-wide design.md. Agents read your tokens, intent, and usage notes — then update them in place.
#9333ea across all components.Saddle Studio
Tokens, components, variants, docs, and MCP — one canvas for your design system, with your real app running live alongside it.
Edit colors, spacing, radius, and shadows with a live preview. Changes sync to your real app via HMR.
--primary-*
Saddle exposes structured component data, tokens, and per-variant docs over MCP. Claude Code edits in place — typed, reviewable, no blind file rewrites.
Cmd-click any element in your running app to edit computed styles inline.
Clone, rename, and edit component variants. Frontmatter ships back to your stories.
Visualize your component dependency graph and explore composition patterns.
Per-component .md files surface usage notes to AI tools and humans.
Saddle sits between the two. Your design system stays in code; your agents stay in the loop. Tokens, props, and docs flow both ways.
Works with any React component library.
Auto-detects components and parses design.md frontmatter.
Auto-detects localhost. Your running app appears inside Saddle.
Figma-style inspector. Changes save to disk and HMR updates your app.
One-click MCP. Claude reads schemas, updates tokens, creates variants.
Everything you need to know about Saddle. Still stuck? Open an issue on GitHub and we'll respond.
Storybook is for documenting components in isolation. Saddle is for editing them — visually, with tokens, while your real app keeps running through HMR. It also exposes structured component data over MCP so AI agents can read and edit your design system in place.
Saddle expects a React project with Vite. It auto-detects your stories file (demo/stories.tsx, **/*.stories.tsx, or a hash-routed demo/App.tsx) and connects to your dev server. Bring-your-own-Vite mode also works if Saddle can't auto-spawn.
One-click install writes .mcp.json to your project root. From there, Claude Code can list components, read variants, edit tokens, and create new variants — all through a typed schema rather than blind file edits.
Token edits and new variants are written back to disk so your app's HMR picks them up — that's the point. Saddle never touches files outside the components and config you've registered in saddle.manifest.json.
Yes. Apache-2.0, source on GitHub.