Autonomous agent · Now in beta

Your design system
has a new employee.

ForgeAI watches your Figma files, updates components, publishes Storybook docs, and runs visual tests — without a single pull request from you.

forge-agent.ts
const agent = watchFigma({
file: "Forge Design System",
onCommit: "update-storybook",
onNewComponent: "generate-pr"
});
 
// ✦ watching figma forge-design-team
// ✦ components: 247 · tokens: 89
// ✦ last sync: 2 min ago · all green
 
Button — variant sync · primary → ghost · PR #341
Token · color.blue.500 updated · docs rebuilt
Visual test · Modal · 0 regressions · passed

The tedious work of design systems, automated.

Design systems drift. Components go stale. Docs fall behind. Every week, engineers and designers burn hours keeping the system honest. ForgeAI replaces that with a live agent that works 24/7.

Watches Figma 24/7

Connects via Figma MCP. Detects component changes, token updates, and variant modifications the moment they land.

Updates components

Generates or updates Web Components, React components, or Stencil libraries. Uses your existing code connect map so nothing is invented from scratch.

Publishes Storybook

Every component change automatically rebuilds and deploys your Storybook. Docs stay in sync without anyone remembering to run the script.

Runs visual tests

Playwright-based visual regression on every change. Flags regressions before they reach production. No manual screenshot diffs.

Opens pull requests

Reviews the diff itself. Adds engineers as reviewers only when human judgment is needed. Opens the PR, writes the changelog entry.

Reports to Slack

Daily digest of what changed, what passed, what needs attention. Replace the weekly design system sync meeting with a Slack message.

From Figma change to production component
in minutes. No human required.

01

Connect Figma

Authenticate with your Figma Organization via MCP. Point ForgeAI at your design system file. It reads component structure, variants, and tokens via the Figma API.

02

Agent decides

When a change is detected, the agent classifies it: token update, new variant, new component, or doc change. Each class has a defined workflow. No rules to write — it learns from your existing repo.

03

Code, test, deploy

The agent writes the component update, runs your existing test suite and visual regression suite, builds Storybook, and opens a PR with a changelog entry describing exactly what changed and why.

04

You review

When the PR is ready, Slack notification. You review the diff, merge it. The agent handled everything upstream. If something looks wrong, one comment on the PR corrects the agent's behavior for next time.

Built on your design system.
Learns from your stack.

ForgeAI doesn't hallucinate components. It reads your Code Connect manifest, knows your token names, and follows your existing conventions. It's not a generic AI — it's an agent trained on your specific design system.

247
components tracked in example config
89
design tokens in sync
0
regressions in last 30 days
forge-agent active
09:41 Button.svelte — variant "destructive" added to Figma
09:41 Generated component · style: destructive · status: clean
09:42 Visual test run · 12 stories · 0 regressions
09:43 PR opened · forgeai/example#341 · assigned: @jives
09:43 Slack notification sent · #design-system

Design systems were supposed to save time.
Now they actually do.

ForgeAI runs your design system like a production service. Components stay current, docs stay fresh, tests stay green — every day, without anyone remembering to run it.