Rams MCP · The full engine, now in your coding agent
noble-assets on GitHub

noble-assets/noble

Reviewed against Rams quality heuristics: accessibility, color, typography, spacing, components, motion, UX, and craft.

1 file reviewed·July 25, 2026

View on GitHub

Top fix

Expand review scope beyond one file to stress-test the pattern

More findings

  • No issues surfaced, suggesting either strong discipline or shallow coverage
  • Single-file scope limits confidence in broader consistency claims

Verdict

A single clean file with a perfect score tells a quiet story: nothing was pushed hard enough to break. The biggest risk is that limited surface area masks whether the underlying pattern holds up at scale.

Files Rams reviewed

api/gen/index.html

Working well

  • Loading the Scalar reference via a pinned commit hash on the CDN URL is a good practice: it avoids silent breaking changes from an unpinned 'latest' tag.

Scored July 25, 2026 with Rams Engine v0.0.3 · Engine changelog
First scored July 22, 2026: 100/100. This rescore on v0.0.3: 98/100.

This page is an automated design review of noble-assets/noble’s UI code: 1 files read against 291 versioned rules covering accessibility, color, typography, spacing, components, UX, motion, and craft. The score is out of 100; confirmed criticals cap it — one at 59, two at 49, three or more at 39.

More design scores

Score your own repo.

Free on public repos, no account. The same engine that scored this page reads your UI code and mints a score page like this one.

Public repos only. The full engine reviews the UI code and mints a public score page — we email you the link too. Already-scored repos open instantly.

Or get a design review on every pull requestInstall Rams