ts-nextjs-app-router

When to Use This Skill

Use when you need to:

• Decide whether a component should be a Server or Client Component
• Structure routes, layouts, and route groups
• Mutate data from a form without a separate API route
• Explain a "Text content did not match" hydration error or a useState used in a Server Component error

Trigger keywords: Server Component, Client Component, use client, use server, Server Action, App Router, route group, layout.tsx, page.tsx, hydration mismatch, Next.js middleware, streaming, Suspense boundary.

Freshness rule: App Router's caching semantics (fetch defaults, revalidatePath/ revalidateTag) have changed across Next.js major versions — recheck the current Next.js docs before relying on a specific caching default.