Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By noemuch
Generate, verify, and update Figma design system components from natural language requests using a compiler-driven pipeline that enforces design system compliance
npx claudepluginhub noemuch/bridge --plugin bridge-dsUse when the user says "setup", "setup bridge", "extract", "extract DS", "onboard", "build knowledge base", "initialize bridge", or is starting Bridge in a project for the first time. Handles the complete bootstrap: pre-flight checks, scaffolding (docs.config.yaml, cron workflow, .bridge/mcp.json), Figma token management (stdin-only), DS extraction via MCP (preferred) or REST (fallback), guide generation, and first commit proposal.
Use when the user requests to design, create, build, generate, or make a new Figma component or screen — including phrases like "make a button", "design a settings page", "build a new card", "generate X". Produces a CSpec, compiles it to a scene graph, executes it in Figma via MCP, and verifies the output.
Use when the user says they adjusted the design in Figma, mentions "fix", "correct", "learn from", "I changed", "diff", "what changed", or wants the system to incorporate manual Figma edits back into the spec. Diffs the current Figma state against the last snapshot, classifies each change as a DS learning or a hardcoded flag, persists learnings, and patches the active recipe.
Use when the user says "done", "ship it", "finish", "complete", "archive", or otherwise indicates the current design is ready to be shipped. Runs final verification (Gate B), archives the CSpec, updates history, extracts a recipe when eligible, and cleans up temp files.
Use when any Bridge command is invoked (make, fix, done, setup, drop, status) or any Figma / design-system / compiler / Bridge workflow topic is raised. Sets command priorities and iron laws (compiler-only, semantic tokens only, verification-before-ship).
Requires secrets
Needs API keys or credentials to function
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Design System compliance harness for Claude + Figma. Enforces library-first components, token binding, and automated QA — so AI-generated designs stay on-spec.
Plugin that includes the Figma MCP server and Skills for common workflows
Creates comprehensive design systems with typography, colors, components, and documentation for consistent UI development. Use when establishing design standards, building component libraries, or ensuring cross-team consistency.
Token generators, component patterns, accessibility guidance, and framework integrations
Build, document, and maintain scalable design systems — from tokens and components to accessibility and theming.
Automated design system construction from repository analysis to production-ready implementation.
Compiler-grade trust for AI-generated Figma.
Deterministic compiler · Living KB · MCP-native
Discussions · Issues · Contributing · Security · Changelog
Bridge compiles your design-system intent into Figma output that's guaranteed DS-compliant by construction — not by verification. 26 Figma API rules enforced automatically by a local compiler. Zero hardcoded values, zero raw Plugin API code, zero AI hallucinations.
Three pillars: a deterministic compiler (the moat), conversational UX via Claude Code skills (make / fix / done), and a living KB continuously synchronized with Figma via cron.
Design components and screens from natural language inside Claude Code. Bridge handles the rest:
# In Claude Code, inside your DS repo:
make a settings screen for account information
Bridge produces:
Every output uses your real components, bound variables, and text styles. Zero hardcoded values.
Iterate with fix (capture manual Figma edits as learnings). Ship with done (archive + extract recipes).
Bridge keeps your knowledge base continuously synchronized with Figma.
setup bridge in Claude Code bootstraps your DS repo: registries, cron workflow, all in one flow.The KB lives in your repo at bridge-ds/knowledge-base/registries/. Point your AI client at this directory or read it programmatically. Your generated code uses tokens, variants, and composition rules correctly — because it reads the source of truth, not guesses.
In Claude Code, any session (one-time install):
/plugin marketplace add noemuch/bridge
/plugin install bridge-ds
In your DS repo:
cd /path/to/ds-repo && claude
setup bridge
One phrase. The skill handles pre-flight, scaffolding, extraction, GitHub secret, first commit, and optional cron test. ~10 minutes end-to-end.
Upgrading from v5.x? See BREAKING.md for the v6 migration guide.
| Layer | Technology | Description |
|---|---|---|
| Workflow | Claude Code Skills | Five focused skills (see Skills below) |
| Spec | CSpec YAML | Structured, human-readable compilable specifications |
| Compiler | TypeScript | Scene graph JSON → Figma Plugin API code (26 rules enforced) |
| Transport | MCP | figma-console-mcp (preferred) or official Figma MCP server |
| Target | Figma Desktop / Cloud | Production-ready designs in your real DS library |
| Memory | Knowledge Base | Registries, guides, recipes, learnings — per-project |
You describe → Claude writes CSpec → Compiler resolves tokens → MCP → Figma