HighFile-scopeJavaScript / TypeScript Plug & play

Use next/image with explicit dimensions and alt

Always use the Next.js Image component for images with width/height (or fill) and meaningful alt text. Avoid plain <img> for app assets.

Add to Mesrai Open workspace

Why this matters

Ensures optimization, stable layout (no CLS), and responsive loading.

Bad vs. good

Side-by-side examples engineers can pattern-match during review.

Avoid

<img src="/hero.png" />

Prefer

import Image from 'next/image'
export default function Hero(){ return (<Image src="/hero.png" width={1200} height={600} alt="Product hero" priority />) }

More snippets

Bad

<img src="/avatar.jpg">

Good

<Image src="/avatar.jpg" width={64} height={64} alt="User avatar" />

Related rules

From the same buckets as this rule.

High
Keep 'use client' at the leaf: default to Server Components
Prefer Server Components for pages/layouts and move interactivity to small leaf Client Components. Only add 'use client' where browser APIs or event handlers are strictly necessary.
stack-nextjsstack-react+2
High
Make fetch caching explicit in Server Components
For dynamic data use { cache: 'no-store' } or file-level dynamic = 'force-dynamic'. For ISR use { next: { revalidate: N, tags: [...] } }.
stack-nextjsstack-react+2
High
Middleware only for light auth/rewrites
Keep middleware fast and side-effect free (no DB writes). Narrow the matcher and skip static assets. Use Route Handlers for heavy logic.
stack-nextjsstack-react+2

Why this matters

Bad vs. good

More snippets

Related rules

Keep 'use client' at the leaf: default to Server Components

Make fetch caching explicit in Server Components

Middleware only for light auth/rewrites

Why this matters

Bad vs. good

More snippets

Related rules

Keep 'use client' at the leaf: default to Server Components

Make fetch caching explicit in Server Components

Middleware only for light auth/rewrites