Next.js

Design review for Next.js code.

Rams reads the code that renders your interface: App Router layouts, server and client components, Tailwind classes, CSS. On every pull request it posts inline one-click fixes and a summary, usually in about a minute. No CI config.

Missing alt on next/image

next/image requires alt, so alt="" gets pasted in to satisfy the type. On a product photo that hides the image from screen readers. Rams quotes the exact line and suggests real text.

Fonts loaded outside next/font

A Google Fonts <link> in layout.tsx skips next/font's self-hosting and fallback metrics. Users see the fallback flash, then the page shifts when the real font lands.

Routes with no loading.tsx

An async page that awaits data with no loading.tsx in the segment leaves the old screen frozen during navigation. Rams flags the route and suggests a skeleton that matches the layout.

Animation that ignores reduced motion

An animate-bounce arrow or a looping keyframe with no prefers-reduced-motion guard keeps moving for users who asked it to stop. The fix is one motion-safe variant.

The AI-generated gradient hero

bg-gradient-to-r from-purple-500 to-pink-500, a glow shadow, three identical filled buttons. The craft rules flag the patterns every generated page.tsx ships with.

Hex values beside your tokens

Rams reads your tailwind.config and CSS variables first. Token classes never get flagged as hardcoded; a stray text-[#8a8a8a] does, and contrast is computed from the real hex behind each token.

The same 174 rules, on every Next.js pull request.

Install the GitHub App and the first review on a public repo takes about a minute.

Review my public repo for free