mozg.betaSign in

explore / Web & frontend / mozg

Next.js App Router

Answer questions about building Next.js applications with the App Router as documented today: routing, layouts, server and client components, data fetching and caching, server actions, and the current API surface — not the Pages Router era the models memorised.

374 notes · updated 2026-08-04 · trained 63%

Ask it things like

answers 17/26 on its latest exam · anti-bluff 2/3
If a function wrapped with 'use cache' reads cookies or headers, what happens?Data Fetching & Caching✓
Explain 'use cache: private' and when it's needed instead of regular 'use cache'.Data Fetching & Caching✓
How do layout.js files nest in the App Router, and what happens to the layout when navigating between siblings?Routing & Navigation✓
Can a Client Component directly import and call a function from a file marked with 'use server'?Server & Client Components✓
If I import a Client Component (marked with 'use client') into a Server Component, what happens?Server & Client Components✓
What is the Static Shell in Partial Prerendering, and why is it important?Streaming & Performance✓
If a component is wrapped in a Suspense boundary with a fallback, how does that interact with Partial Prerendering?Streaming & Performance✓
What are Intercepting Routes, and what's a real-world use case?Advanced Patterns✓

What is inside

asking this brain searches all 2
Next.js · API referenceAnswer questions about the Next.js API surface exactly as specified: components, file conventions, functions, directives and config options.1944 notes—Next.js · GuidesAnswer questions from the Next.js guides: authentication, caching, data fetching patterns, migration, deployment and testing.1308 notes—
use this brain
# sign in to get a token
$ claude mcp add --transport http mozg \
https://mozg.sh/mcp --header "Authorization: Bearer …"
> use mozg/nextjs — …
Get a token

Use this brain

Sign in and add it, and every agent you have connected can read it — nothing to download, and it stays current as the author updates it.

Sign in to add it

What it can answer

26 checks
63%
▲Build & Deployment3 / 5
▲Data Fetching & Caching3 / 6
✓Routing & Navigation3 / 3
▲Error Handling & Special Files2 / 3
▲Server & Client Components2 / 3
✓Streaming & Performance2 / 2
▲Advanced Patterns1 / 2
▲Server Actions & Route Handlers1 / 2
exam badge — share this score →

Inside

  • Dynamic rendering definition · data-fetching-caching/server-components
  • Code Splitting definition · app-router/file-conventions
  • Client Component definition and capabilities · app-router/server-client-components
  • Client Cache definition and invalidation methods · data-fetching-caching/caching
  • Catch-all segments syntax and purpose · app-router/file-conventions
  • Cache Components feature and caching functions · data-fetching-caching/caching
  • Import Aliases for module paths · getting-started/module-paths
  • Client Bundles definition · app-router/file-conventions
  • App Router definition and features · app-router/file-conventions
  • Client-side navigation with Link component · app-router/navigation
  • Revalidation definition and methods · data-fetching-caching/caching
  • App Shell caching behavior · app-router/proxy
  • Build time definition · app-router/file-conventions
  • Dynamic route segments syntax · app-router/file-conventions

Licence

CC BY-NC-SA 4.0

Use it, copy it, build on it, with credit. Selling it is not allowed.