▀▄▀▄▀▄▀▄▀▄
▄▀▄▀▄▀▄▀▄▀
▀▄▀▄▀▄▀▄▀▄
▄▀▄▀▄▀▄▀▄▀
Ingest from your repo
Connect GitHub. Tokens, components, and rules become structured blocks — not another static doc.
Learn moreNew: your design system is now callable. Open the wiki in an agent browser and it hands over the rules. SEE IT
Approve your design system in the browser. Developers pull what's promoted.
Define constraints in the wiki, not endless Figma specs. Spacing, type scales, and tokens — edited visually, stored as data.
1// Wiki edits instantly generate raw design tokens2{3 "colors": {4 "signal-orange": "#ff4500",5 "paper-white": "#ffffff"6 },7 "typography": {8 "base": "16px",9 "scale": 1.1510 }11}Stop hunting for hex codes. Pull approved tokens into your repo; CI catches drift.
1# Pull approved tokens into your repo2blocksmith pull --env production34# Validate your codebase against the design system in CI5blocksmith check --fail-on-driftAn MCP server gives coding agents your UI rules — so they only write code that follows them.
1// MCP Tool Request: 2// "What are the rules for a primary button?"3{4 "tool": "get_design_rules",5 "target": "PrimaryButton",6 "response": {7 "bg": "signal-orange",8 "radius": "4px",9 "padding": "12px 24px"10 }11}Developer first
The control plane between Figma, your repo, and your agents.
▀▄▀▄▀▄▀▄▀▄
▄▀▄▀▄▀▄▀▄▀
▀▄▀▄▀▄▀▄▀▄
▄▀▄▀▄▀▄▀▄▀
Connect GitHub. Tokens, components, and rules become structured blocks — not another static doc.
Learn more
┌──────┐
│ ░░░░ │
├──────┤
│ ▒▒▒▒ │
└──────┘
Design leads edit roles, rules, and tokens. Staging stays separate until someone promotes.
Learn more
═════╗
║
╚═════►
Staging → production per block. Diffs, batch promote, roll back.
Learn more
▄▄▄
█ █
███████
█ ▄▄▄ █
███████
blocksmith.lock in your repo. MCP and CI resolve pinned versions — no invented hex mid-session.
Learn moreMCP + CLI
One install. Agents and CI read only what you promoted.
View protocol docs