Rams MCP · The full engine, now in your coding agent

Design eval for agents

Agents write UI.
Rams judges it.

Kill slop in its tracks. Every change scored 0–100 against 308 design rules, fixes handed back as patches your agents apply.

ClaudeOpenAICursorGitHub
PricingPage.tsx
PR #42
38<div className="flex gap-3">
39 <button className="bg-white text-black">Get Started</button>
40 <button className="bg-white text-black">Learn More</button>
41</div>
Ramsreviewed line 39–40UX
 

The whole review, right in your PR.

Every comment includes the issue, its severity, the affected UI area, and a concrete fix, directly inside the pull request where engineers already work.

rams-design-review bot
acme/web-app #42 · Update pricing page
PR score 47/100·Risk High
3 issues found·1 critical·reviewed in 58s
01
Two filled CTAs split focus: the primary action is ambiguousUX

The hero has "Get Started" and "Learn More" both styled as filled white buttons at the same size. Two primary-weight buttons in one row don’t make a hierarchy.

ImpactUsers can’t tell which is primary, so conversion drops on the page’s most valuable click.
Suggested change
<button className="bg-white text-black">Learn More</button>
+<button className="border border-neutral-700">Learn More</button>
02
Stat values use hardcoded hex, bypassing the design systemDesign System

The +12% indicator uses an inline color, hardcoding a value that should live in tokens.

ImpactTheme updates and dark-mode passes silently miss these values, so the product drifts as the system evolves.
Suggested change
<span style={{ color: '#22c55e' }}>+12%</span>
+<span className="text-emerald-500">+12%</span>
03
Feature grid cards are visually identical, with no entry pointUX

All six feature cards share identical weight, color, and spacing. Nothing draws the eye to any single card.

ImpactUsers scan the headings without absorbing the content. The grid reads as a wall, and the strongest claim never lands.
This review doesn't block the merge. Fixing these now avoids accessibility issues, UX regressions, and design-system drift.Rams · Automated Design Reviews

Your team ships UI faster than it’s reviewed.

Design review does not scale with modern frontend velocity. Rams gives every UI change a consistent review before it reaches production.

Prevent competing CTAs

Two primary-weight buttons, no visual ranking, no clear next step. The conversion click splits between actions that look identical.

Prevent low contrast and missing labels

Sub-4.5:1 body text, missing alt attributes, sub-44px targets, suppressed focus rings. Screen-reader and keyboard users get a half-broken page.

Prevent hardcoded hex and one-off spacing

Inline colors that bypass tokens, padding outside the scale, !important overrides on system components. Theme changes silently miss these.

Prevent generic gradients and templated layouts

Purple-to-pink gradients, glow shadows, vague hero copy, identical filled buttons, the output of unedited prompts.

Prevent broken states and duplicate handlers

Submit buttons with no disabled state, double-fired handlers, clickable spans without keyboard support, missing loading states.

Prevent unguarded motion

transition: all watches every property on every render. Animations without prefers-reduced-motion violate WCAG and unsettle users.

Trained on how senior designers actually review.

308 rules across 9 categories. Not linter rules. Review judgments: the bar is human-level design craft, and a whole category exists to catch AI antipatterns. New rules ship every week. Every repo Rams reviews gets sharper without changing a thing.

308
Review judgments, public in the rules
12,747
UI issues caught before merge
37
Craft rules aimed squarely at AI antipatterns
Accessibility24 rules
Alt textFocus indicatorsTouch targetsContrast ratiosKeyboard navScreen-reader labels
Color25 rules
Color tokensOne gray scaleDark modePalette limitsSemantic colorsContrast on bg
Typography40 rules
Type scaleFont smoothingTabular numsLine-heighttext-balanceLetter spacing
Spacing25 rules
Spacing scaleBorder radiusOptical alignmentGap over marginz-index scaleConcentric radii
Components22 rules
Accessible primitivesComponent reuseDesign tokensVariant patternscn() conditionalsTypeScript props
UX64 rules
Loading statesForm validationHit areasButton semanticsInput font sizeEmpty states
Motion51 rules
prefers-reduced-motionInterruptible transitionsScale on pressExit animationsNo blur > 20pxEasing
Craft37 rules
No gradientsNo glowNo transition:allVisual monotonyNo placeholder textisolation:isolate

A design engine that keeps improving.

Eight specialist reviewers and 308 encoded judgments today, with new rules added every week. Re-reviews verify the fixes you ship, so the score climbs as the work lands. The engine finds the issue. AI explains the review.

Perpetual design engine

New review judgments are authored and refined every week. As the engine encodes more of how senior designers think, every project it reviews gets sharper automatically, without you changing a thing.

Eight reviewers, one per discipline

Accessibility, color, type, spacing, motion, components, UX, and craft each review every PR with their own rules, the way a real design team splits the work.

Grounded in your actual code

Contrast ratios are calculated from real hex and token values, and every finding quotes the line it came from. Two passes: fast triage, then a deep, line-level review of the highest-risk files.

Every finding ships with a fix

Issues are severity-rated and arrive with an inline suggestion you can commit straight from the pull request. No context-switching.

AI gives you an opinion. Rams keeps score.

Opinions are useful once. Scores become operational. Every review produces a consistent design score across PRs, repos, and releases, so teams track design quality over time instead of debating one-off opinions.

Verified fixes

Re-reviews check every finding you fixed, by name. The score climbs as the work lands, and a clean pass says so: all flagged issues resolved.

A number you can trust

The same 308 rules on every review, and criticals cap the score — one holds it to 59, two to 49, three or more to 39. A 60 or above always means zero critical issues.

The whole team’s gate

Every pull request from every contributor gets reviewed, humans and agents alike. Nobody has to install anything.

The honest comparison: Rams vs design skills

The standards your product relies on.

Accessibility findings map to named W3C requirements, not house opinion. When Rams flags contrast, a missing label, or unguarded motion, it is pointing at the standard behind the call.

W3CWCAG 2.1 AA
Contrast

Contrast, labels, focus order, and heading structure: the quiet failures that lock real people out of your product.

W3C · WAIWAI-ARIA
Semantics

Roles, names, and states on every interactive element, so assistive tech can announce each control your users reach for.

W3C · CSSprefers-reduced-motion
Motion

Animation that ignores motion preferences: the unguarded transitions and autoplay that leave motion-sensitive users dizzy or unwell.

W3CWCAG 2.2
Targets

Target size and focus appearance: the newest criteria, checked before most teams have adopted them.

W3C · WAIWAI-APG
Keyboard

How dialogs, menus, and tabs should behave for keyboard users, from focus trap to escape key.

Cory Etzkorn

Rams brings the missing piece to AI tooling: taste.

Cory Etzkorn · Founder at Soulmate,
previously Design Engineer at Notion

Start free. Upgrade when Rams becomes part of your merge process.

Free on public repos. Flat monthly tiers from $39, no per-seat fees. Every tier runs the full engine.

Free

For trying Rams on your open-source work. One public repo, no credit card, no commitment. Just install and go.

$0
Install free
GitHub App on 1 public repo
30 reviews / month, PRs + MCP
The full 308-rule engine
Inline one-click fix suggestions
Re-reviews that verify your fixes
Score history in the dashboard
MCP API keys included

Solo

For your next big idea or side project. One private repository at a time, with the full review on every pull request.

$39/mo
Get started
GitHub App on 1 private repo
50 reviews / month, PRs + MCP
The full 308-rule engine
Inline one-click fix suggestions
Re-reviews that verify your fixes
Score history in the dashboard
Standard support

Team

Popular

For teams shipping real product. Unlimited repos, unlimited people, one flat price. Go over and it keeps working.

$499/mo
Get started
Unlimited public & private repos
Unlimited team, no per-seat fees
500 reviews / month included, PRs + MCP
Then $0.90 per review, never a wall
The full 308-rule engine
Inline one-click fix suggestions
Re-reviews that verify your fixes
Monthly design-drift report
Priority support
Review pack · $24 one time

25 reviews at $0.96 each, no subscription. Credits never expire and work on any plan. For launch weeks and backlog sweeps.

Buy a pack
Enterprise · Custom

For the whole organization. Custom rules, SSO, dedicated SLA.

Contact us

Catch design regressions before your users do.

Score your repo free in about two minutes, no account. Or install Rams and every pull request gets the review.

Score my repo for freeInstall Rams