Run any Skill in Manus with one click

nextjs-server-components

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.

Run Skill in Manus

Stars504

Forks148

UpdatedMay 20, 2026 at 02:09

Source

HoangNguyen0403

HoangNguyen0403/agent-skills-standard

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

File Explorer

4 files

SKILL.md

readonly

name	nextjs-server-components
description	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.
metadata	{"triggers":{"files":["app/*/.tsx","src/app/*/.tsx","app/*/.jsx","src/app/*/.jsx"],"keywords":["use client","Server Component","Client Component","hydration"]}}

Server & Client Components

Priority: P0 (CRITICAL)

[!WARNING] If project uses pages/ directory instead of App Router, ignore this skill entirely.

App Router uses React Server Components (RSC) by default.

Workflow: Add Server/Client Component Split

Default to RSC — Async Server Components for data fetching.
Push 'use client' to leaves — Interactive leaf nodes only (Button, Form, Chart). Keep layouts/pages as Server Components to maximise RSC benefits.
Compose via children — Pass Server Components as children to Client Components.
Serialize props — Server-to-Client props must be serializable (no functions, Dates, or Classes).
Guard secrets — Import server-only in modules with sensitive logic.

Composition Pattern Example

See implementation examples

Implementation Guidelines

Async RSCs: Fetch directly in async Server Components — await db. queries, await params for route segments.
Data Fetching: fetch with cache: 'no-store' or revalidate: 0 opts out of static rendering.
Streaming: Wrap slow async components in <Suspense>. Use loading.tsx for route-level skeletons.
Hydration: Server sends HTML + RSC payload; client hydrates only Client Components. Server Components: zero JS in client bundle.
Server-in-Client: Cannot import Server Component into Client Component.
Fix: Pass as children prop. See Composition Example.

Anti-Patterns

No secrets in Client Components: Use server-only package to prevent accidental bundling.
No full DB objects passed to client: Minimize serialized props; pass IDs when possible.
No useState/useEffect in Server Components: These Client Component-only hooks.
No 'use client' at tree root: Push boundary to leaf components.

References

Server/Client Composition Example

More from this repository

same repository

common-business-requirements

HoangNguyen0403/agent-skills-standard

Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.

2026-05-25504

common-product-requirements

HoangNguyen0403/agent-skills-standard

Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.

2026-05-25504

common-software-requirements

HoangNguyen0403/agent-skills-standard

Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.

2026-05-25504

brainstorm-feature

HoangNguyen0403/agent-skills-standard

Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.

2026-05-25504

design-solution

HoangNguyen0403/agent-skills-standard

Turn an approved PRD or implementation goal into SRS/FRS technical requirements (How), architecture, contracts, and verification decisions.

2026-05-25504

plan-feature

HoangNguyen0403/agent-skills-standard

Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.

2026-05-25504

name	nextjs-server-components
description	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.
metadata	{"triggers":{"files":["app/*/.tsx","src/app/*/.tsx","app/*/.jsx","src/app/*/.jsx"],"keywords":["use client","Server Component","Client Component","hydration"]}}

Server & Client Components

Priority: P0 (CRITICAL)

[!WARNING] If project uses pages/ directory instead of App Router, ignore this skill entirely.

App Router uses React Server Components (RSC) by default.

Workflow: Add Server/Client Component Split

Default to RSC — Async Server Components for data fetching.
Push 'use client' to leaves — Interactive leaf nodes only (Button, Form, Chart). Keep layouts/pages as Server Components to maximise RSC benefits.
Compose via children — Pass Server Components as children to Client Components.
Serialize props — Server-to-Client props must be serializable (no functions, Dates, or Classes).
Guard secrets — Import server-only in modules with sensitive logic.

Composition Pattern Example

See implementation examples

Implementation Guidelines

Async RSCs: Fetch directly in async Server Components — await db. queries, await params for route segments.
Data Fetching: fetch with cache: 'no-store' or revalidate: 0 opts out of static rendering.
Streaming: Wrap slow async components in <Suspense>. Use loading.tsx for route-level skeletons.
Hydration: Server sends HTML + RSC payload; client hydrates only Client Components. Server Components: zero JS in client bundle.
Server-in-Client: Cannot import Server Component into Client Component.
Fix: Pass as children prop. See Composition Example.

Anti-Patterns

No secrets in Client Components: Use server-only package to prevent accidental bundling.
No full DB objects passed to client: Minimize serialized props; pass IDs when possible.
No useState/useEffect in Server Components: These Client Component-only hooks.
No 'use client' at tree root: Push boundary to leaf components.

References

Server/Client Composition Example