Catch UI bugs before they merge.
Rams reviews your pull requests and flags UI issues that reduce conversion, break accessibility, and create design-system drift — before they ship.
Free for public repos. No credit card. Works on your first PR in minutes.
acme/web-app #42 · Update pricing page
3 issues · 1 critical
Design Review — 3 issues found
Score: 47/100 · Risk level: High
Two filled CTAs split focus — primary action is ambiguous·UX
The hero has "Get Started" and "Learn More" both styled as filled white buttons at the same size. Two primary-weight buttons in the same row is not a hierarchy.
Impact: Users can't tell which is primary → conversion drops on the page's most valuable click.
Fix:Use a single filled CTA for the primary action; demote secondary actions to ghost or text-link style.
Stat values use hardcoded hex — bypasses the design system·Design System
The +12% indicator uses style={{ color: '#22c55e' }} inline, hardcoding a color that should live in tokens.
Impact: Theme updates and dark-mode passes silently miss these values → product drifts visually as the system evolves.
Fix:Replace inline hex with a semantic token class like text-emerald-500.
Feature grid cards are visually identical — no entry point·UX
All six feature cards share identical weight, color, and spacing. Nothing draws the eye to any single card.
Impact: Users scan headings without absorbing content → the grid reads as a wall and the strongest claim never lands.
Fix:Vary one card's scale or treatment to create a focal point, or order by importance with the strongest claim first.
Your team is shipping UI faster than it's being reviewed.
AI tools and fast iteration make it easy to ship product — and easy to ship confusing, inconsistent, or inaccessible UI. Most teams don't have a senior designer reviewing every pull request. Issues slip through and compound over time.
The UI issues your team misses when shipping fast
Multiple CTAs compete → users don't know where to click
Two primary-weight buttons in the same row, no visual ranking, no clear next step. The conversion click is split between actions that look identical.
Low contrast and missing labels → broken UX for real users
Sub-4.5:1 contrast on body text, missing alt attributes, sub-44px touch targets, focus rings suppressed without replacement. Screen readers and keyboard users get a half-broken page.
Hardcoded hex and one-off spacing → product becomes inconsistent
Inline style colors that bypass tokens, padding values outside the spacing scale, !important overrides on system components. Theme changes silently miss these.
Generic gradients and templated layouts → product looks AI-generated
Purple-to-pink gradients, glow shadows, vague hero copy, identical filled buttons. The output of unedited prompts.
Broken states and duplicate handlers → UI behaves incorrectly
Submit buttons with no disabled state, double-fired onSelect+onClick, clickable spans without keyboard support, missing loading states.
Unscoped transitions and no reduced-motion guard → janky UX
`transition: all` watches every CSS property on every render. Animations without `prefers-reduced-motion` violate WCAG 2.3.3 and unsettle users on the move.
Trained on how senior designers actually review code
109 rules across 8 categories — accessibility, color, typography, spacing, components, UX, motion, and AI-generated patterns. Not linter rules. Review judgments.
A design skill file gives advice. Rams runs reviews.
Keep your design prompts. Rams ensures your product actually follows them.
Free skill file
- Has to be invoked manually
- Generic — not aware of your codebase
- Easy to ignore mid-PR
- Doesn't comment on pull requests
- No way to enforce standards
- No history or memory across reviews
- Goes stale when rules change
Rams
- Runs automatically on every pull request
- Repo-aware — sees your actual code
- Posts inline comments with one-click fixes
- Top-level review summary at the top of every PR
- Optional merge blocking on critical issues
- Review history kept per workspace
- Always on the latest ruleset
Run Rams on your repo in 30 seconds.
No config. No setup. No credit card. Free for public repos.
Review my public repo freeReal reviews on real codebases
We ran Rams on shadcn/ui, cal.com, Supabase, and Next.js. Read what it found.
The component library powering most modern Next.js apps.
Mention removal buttons have no accessible name for screen readers
Dashboard images have generic alt text that communicates nothing
Outer FieldLabel's htmlFor points to nothing — label is unassociated
The open source scheduling platform.
Dual fake checkbox inputs break keyboard and screen reader state
Popover content removes outline without a replacement focus style
Label-as-button has no keyboard focus indicator visible to users
The open source Firebase alternative — Studio dashboard.
Bar fills convey data with no accessible text alternative
Trigger button uses arbitrary `!pr-1` override instead of a size variant
The React framework — DevTools overlay components.
NextLogo trigger has no accessible name surfaced at this level
Success state communicates via color alone — no visible label change renders
Span trigger wrapper breaks keyboard and screen-reader semantics for interactive children
From install to review in minutes
Install the GitHub App, open a pull request, get a review back in about a minute. No CI configuration, no API keys, no workflow files.
Rams becomes part of your pull request workflow.
- Step 1
Install GitHub App
One-click install. No CI files, no API keys.
- Step 2
Open a PR
Push UI changes to any branch and open a pull request.
- Step 3
Rams reviews UI changes
Inline comments + a top-level summary land within ~60 seconds.
- Step 4
Fix issues before merge
One-click apply on each suggestion, or merge through anyway.
Works with your stack
JSX, TSX, Vue SFCs, Svelte components, Angular templates, CSS, SCSS. Next.js app dir, SvelteKit routes, Vue pages, Angular components, React Native screens.
Don't see your framework?
Request support and we'll add it.
Built for teams shipping UI without enough design review
Founder-led teams
Shipping fast, no time for manual design review.
AI-heavy teams
Cursor, Copilot, v0 generate code. Rams catches what they miss.
Design engineers
A second pair of eyes between manual reviews.
Agencies
Consistent quality across client work without staffing senior designers per project.
“Rams brings the missing piece to AI tooling: taste.”
Cory Etzkorn, Founder at Soulmate · previously Design Engineer at Notion
Pricing
Start free. Upgrade when Rams becomes part of your workflow.
For trying Rams on your open source. No credit card.
For your next big idea. One private project at a time.
For teams building real product. Every repo. One flat price.
For teams moving fast. 750 reviews a month.
For the whole organization. Custom rules, SSO, dedicated SLA.
Stop shipping UI issues your users will notice.
Rams reviews UI changes before they merge so your product stays
consistent, accessible, and usable.