nextjs-server-components

Included with Lifetime

$97 forever

React Server Components patterns for Next.js 16. Server vs Client boundaries, async components, data fetching, serialization rules, streaming with Suspense.

Web Dev

What this skill does


# Next.js Server Components

Server Components are the default rendering model in Next.js 16 with React 19.

## Agent Workflow (MANDATORY)

Before ANY implementation, use `TeamCreate` to spawn 3 agents:

1. **fuse-ai-pilot:explore-codebase** - Analyze existing component boundaries
2. **fuse-ai-pilot:research-expert** - Verify latest RSC docs via Context7/Exa
3. **mcp__context7__query-docs** - Check Next.js 16 RSC patterns

After implementation, run **fuse-ai-pilot:sniper** for validation.

---

## Overview

### When to Use

- Deciding between Server and Client Components
- Fetching data directly in components without API routes
- Implementing streaming and progressive rendering
- Passing data across the server/client boundary
- Using async components with direct database access

### Why Server Components

| Feature | Benefit |
|---------|---------|
| Zero client JS | Components never ship to the browser bundle |
| Direct data access | Query databases, read files without API layer |
| Streaming | Progressive rendering with Suspense boundaries |
| Automatic code splitting | Client Components are lazy-loaded by default |
| SEO-friendly | Full HTML rendered on the server |

---

## Critical Rules

1. **Server Components are default** - No directive needed
2. **`'use client'` only when needed** - Hooks, events, browser APIs
3. **Never import server-only into client** - Use `server-only` package
4. **Props must be serializable** - No functions, classes, or Dates across boundary
5. **Async components are server-only** - Client Components cannot be async
6. **Colocate data fetching** - Fetch where the data is consumed

---

## Best Practices

1. **Push client boundaries down** - Keep `'use client'` as deep as possible
2. **Composition pattern** - Pass Server Components as `children` to Client
3. **Use `server-only`** - Prevent accidental client imports of secrets
4. **Parallel fetching** - Use `Promise.all()` for independent data
5. **Cache with `use cache`** - Cache expensive server computations
6. **Stream with Suspense** - Wrap slow components for progressive loading

---

## Reference Guide

| Need | Reference |
|------|-----------|
| Server vs Client patterns | [rsc-patterns.md](references/rsc-patterns.md) |
| Streaming and Suspense | [streaming.md](references/streaming.md) |
| Data fetching in RSC | [rsc-patterns.md](references/rsc-patterns.md) |
| Loading states | [streaming.md](references/streaming.md) |

Files: 3

Size: 7.9 KB

Complexity: 26/100

Category: Web Dev

Source: https://github.com/fusengine/agents/tree/main/plugins/nextjs-expert/skills/nextjs-server-components

Related in Web Dev

generating-lwc-components

Included

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.

Web Devscripts

document-processor-api

Included

Process documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.

Web Devscripts

nutrient-document-processing

Included

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.

Web Devscripts

accelint-nextjs-best-practices

Included

Next.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.

Web Devscripts