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

shamahdev/shamahdev

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

1 file reviewed·August 6, 2026

View on GitHub

Top fix

Remove negative word-spacing from the global html/body rule

See the fix

Verdict

A well-structured type token system is undone by one reckless global rule. Negative word-spacing on html/body crowds every word on every page, the single biggest risk to an otherwise clean 98-score setup.

Files Rams reviewed

src/styles/global.css

98/100

Typography

1 serious
TypographySerious

src/styles/global.css:11

Negative word-spacing on all body text crowds every word boundary

The global html, body rule sets word-spacing: -0.05em, applied site-wide to every paragraph, heading, and label that inherits this base style. Tightening word gaps below the browser default makes words run closer together across the entire page.

Why it matters

Reading speed drops and scan clarity degrades on every block of text on the site, not just one component, because the compressed word boundaries make it harder to parse where one word ends and the next begins, especially at body-text sizes.

Fix

Remove negative word-spacing from the global base rule and let text use normal browser spacing.

font-family: var(--primary-font), Arial, Helvetica, sans-serif;
word-spacing: -0.05em;
font-feature-settings: "rlig" 1, "calt" 1;
font-family: var(--primary-font), Arial, Helvetica, sans-serif;
font-feature-settings: "rlig" 1, "calt" 1;

Accessibility

No issues found

Color

No issues found

Spacing

No issues found

Components

No issues found

Motion

No issues found

UX

No issues found

Craft

No issues found

Working well

  • Defining --primary-font and --secondary-font as semantic CSS variables instead of hardcoding font names in each component is a clean token pattern: swapping typefaces later means editing one place in :root, not hunting through every component file.

Scored August 6, 2026 with Rams Engine v0.0.4 · Engine changelog

This page is an automated design review of shamahdev/shamahdev’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