Review a Next.js component for server/client boundaries
Checks an App Router component for misplaced "use client", leaked server-only code, hydration risks and avoidable client bundle weight.
Prompts are text you copy into your own assistant. KitLocal does not run them.
Fill in the variables
What you type stays in this browser. It is not added to the URL, saved, or sent anywhere.
Preview
Still needed: Component code
Review this Next.js (version 16, App Router) component.
Cache Components enabled: no
Check and report, with line references:
1. Is "use client" necessary, and is it as low in the tree as possible?
2. Does any client code import server-only modules, secrets, or Node built-ins?
3. Can browser-only values (window, localStorage, Date.now, Math.random) cause a hydration mismatch?
4. Are props crossing the server → client boundary serializable?
5. Are there heavy dependencies that could be loaded lazily?
6. Are params / searchParams / cookies / headers handled with the async APIs for this version?
Answer "no issue" explicitly for items that are fine. Do not rewrite the file unless asked;
propose minimal diffs.
```tsx
{{component}}
```
Purpose
Catch server/client boundary mistakes in Next.js App Router code before they become runtime errors or bundle bloat.
When to use it
- You added or moved a component and are unsure where "use client" belongs.
- A page hydrates oddly or the client bundle grew.
What to prepare
- The component (and its direct imports if short), plus the Next.js version.
Expected output
A numbered list (items 1-6) with verdict, evidence and a minimal diff where needed.
About this catalog
Bundled snapshot · published Nov 15, 2026, 6:05 AM · Catalog revision 5bc079fe355af2214bc0
Showing the snapshot bundled with this app (no content source is configured). Newer content may exist at the source.