Stop fighting with your generated UI.

We create a that establishes a single source of truth on one canvas. You are made aware of changes and we make sure your agents don't drift.

Problem

Your design drifts without you noticing.

Each iteration drifts from your design, more than the last. Over time it adds up.

No visibility

You can't see all the rules, styles and components your agents are using.

Too many versions

Code, Figma, and your agents rule files each drift into a slightly different system.

Drift adds up

Every off-system value gets copied, and you pay for it later in QA and bug hunts.

Sound familiar?

You're not the only one fighting your agent.

Real posts from people fighting the drift.

Solution

One design contract for your team and your agents.

Grum shows your team what's really in the code and lets them review every change, while your agents stay on-system by following the rules.

For humans

See what your code really ships, clean it up once, and let Grum test it for drift automatically.

For agents

Grum lives inside Claude, Codex, and Cursor, so your agents reuse what exists instead of drifting.

  • Connect GitHub, Figma, MD files, or a live URL
  • See every style, component, and pattern your code ships
  • Merge near-identical colors and styles into one token
  • Connect your agents through MCP and CLI
  • Scale your team without re-training them and their agents
Coming Soon
  • Keep every agent-facing rule and guideline in Grum, synced to your repo
  • Manage multiple design systems in one workspace
  • Govern all the components and drift reviews across your company
  • Start with an already setup design system from scratch

Getting started

Install Grum with a prompt.

Connect Claude, Codex, or Cursor, or use npx for CLI.

First, install Grum in Claude, Codex or Cursor.

System Generation

Your design system, built from your .

Skills aren't enough. We combine CSS, code, and skills, to create contracts you can visualize. Click colors or components to see variants, tokens, and location.

Team Awareness

Know where every change landed.

New components and styles go to review before they spread. Real drift gets flagged with a fix prompt.

Under the hood

Every line, checked against the contract.

Each value is deterministically evaluated in milliseconds. Grum nudges agents while making sure designers are informed.

grum.so/design-system
Grum
Styles
Components
Patterns
Guidelines
Review1
Your design system
contract v14
Built from your rules. New patterns land here for review.
Color tokens
purplenew token from your agentPending review
primary/baseapproved tokenApproved
text/primaryapproved tokenApproved
Buttons
Purchase Purple squareNew pattern from your agent Pending review
Request changesApprove
PurchasePrimaryMain actionApproved
PurchaseSecondarySupporting actionApproved
PurchaseGhostQuiet actionApproved
button / purple-square
Designer
10:0752
Purple buttonwebapp
···
Worked for 3s

Connected Grum and loaded your design contract, v14: 12 tokens, 4 buttons.

Worked for 1s

Grum is set up. Every UI change I make gets checked against it.

Grum checked 8 lines in 42 ms and found 3 that don't match the contract. Purple and square corners aren't in it. How should I proceed?
L2background #654dc4 ≠ #cb3451
L5radius 0px ≠ 8px
L11hover #7c3aed ≠ #b32e47
Add as new pattern
Add a purple token and a square purple button to the contract.
Request review
Keep it and ask a reviewer to approve the off-contract styles.
Use the contract button
Skip purple and use the approved Primary button.
SkipSubmit
Needs your input
Add as new patternin design review
✓Balazs approved Purple square and the purple token. Contract is now v15.
Reply to Claude
1 Ask agent for change 2 Grum checks code in ~40 ms 3 Decide how to proceed or skip 4 Designers are always aware

Certainty

A check that does not guess.

Agents get confused by contradictions in rules or CSS that compounds over time. Grum matches the implementation to the contract, every time.

✕ SKILLS AND INFERENCE ONLY ✓ WITH CONTRACT Add a button Purchase Purchase Purchase Purchase Purchase Purchase Purchase Add a button Purchase Purchase Purchase Purchase Purchase Purchase Purchase A different UI every run. Plausible, never proven. The same UI every run. Code matched to the contract, not inferred.

Audience

Less time chasing pixels.
More time shipping product.

One contract that designers define, engineers trust, and agents follow.

Design engineers

You write the rules, but you're the only one checking the agents. Grum is your second pair of eyes.

Engineers

Your PR passes tests, then bounces back over a 4px button. Grum gives your agent the fix while you work.

Designers

Your handoff quietly changes, and you find out in production. Grum flags new elements before they spread.

Questions

Would you like to know more?

How the contract is built, what you can connect, and what happens when something drifts.

What's in a Design Contract?

The components, tokens, colors, styles, and fonts your product is allowed to use. Grum drafts it from your repo, existing guidelines, and live site, and your design lead decides what makes the cut. Learn more about design contracts.

What can I connect today?

GitHub, Figma, MD files, and live URLs as sources. Grum works insude your agents and tools, including Claude, Codex, Cursor, and terminal CLI. More integrations are on the roadmap.

Why a "contract" and not just guidelines?

Agents treat guidelines and markdown files like a conversation, more suggestion than rule, and often favor existing code when they fill their context. It also gets very confused if there are condractions in code or css when designs shift. A contract stays binding at every step, iteration, and release, without burning tokens on constant re-reviews.

When the repo, design system, and live site disagree, which one wins?

You decide. Grum shows what exists in each source, and your team picks the true north. That becomes the contract. More importantly, it alerts you when there is a contradiction.

What happens when Grum finds drift?

Grum tells you where it is, and show you what t looks like, so no one has to hunt for it. Leads can accept it into the contract or reject it, and your agent picks up the decision on its next iteration.

Will Grum block my agent or slow down development?

No. By default, the agent flags mismatches in chat and suggests options to delay, change, or update the review, and keeps building either way. Owners who want more control can limit the options to delaying or ignoring for a set time.

Does Grum catch drift before or after code is written?

Both. It guides your agent in real time while it builds, and the Drift view catches anything that slips through, including legacy code, like hard-coded values or near-identical shades of red.