skills/nextjs/nextjs-server-components/SKILL.md
Build async React Server Components and place 'use client' boundaries at leaf nodes for interactivity in Next.js App Router. Use when deciding RSC vs Client Component, composing server data into client wrappers, or fixing hydration errors.
npx skillsauth add hoangnguyen0403/agent-skills-standard nextjs-server-componentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
[!WARNING] If project uses
pages/directory instead of App Router, ignore this skill entirely.
App Router uses React Server Components (RSC) by default.
'use client' to leaves — Interactive leaf nodes only (Button, Form, Chart). Keep layouts/pages as Server Components to maximise RSC benefits.children to Client Components.server-only in modules with sensitive logic.See implementation examples
await db. queries, await params for route segments.fetch with cache: 'no-store' or revalidate: 0 opts out of static rendering.<Suspense>. Use loading.tsx for route-level skeletons.children prop. See Composition Example.server-only package to prevent accidental bundling.useState/useEffect in Server Components: These Client Component-only hooks.'use client' at tree root: Push boundary to leaf components.testing
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
documentation
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
development
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
data-ai
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.