react-server-components
/react-server-components
Use this skill when building modern React applications utilizing React Server Components (RSC) to reduce client JavaScript and stream data.
- Author
- nextboxis ↗
- Repository
- library-skill-agents ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use this skill when building modern React applications utilizing React Server Components (RSC) to reduce client JavaScript and stream data.
Original author description
Use this skill when building modern React applications utilizing React Server Components (RSC) to reduce client JavaScript and stream data.
How it works
- When to use
- Prerequisites
- Step-by-step workflow
- Commands / code examples
- Common mistakes & pitfalls
- Verification checklist
- Related skills
SKILL.md preview
---
name: react-server-components
description: Use this skill when building modern React applications utilizing React Server Components (RSC) to reduce client JavaScript and stream data.
---
# React Server Components
## When to use
Use this skill when building data-heavy web applications with Next.js or React 19, where minimizing client bundle size and accessing backend resources directly is essential.
## Prerequisites
- Node.js 18.17+ and Next.js 14+ or an RSC-compatible bundler.
- Understanding the boundary between server execution and client hydration.
## Step-by-step workflow
1. **Establish component boundaries**: Default all components to Server Components. Add `'use client'` only when interactive event handlers or hooks are required.
2. **Fetch data directly in components**: Use async/await directly in Server Components to query databases or internal services without client waterfalls.
3. **Keep client bundles minimal**: Pass server data down to Client Components as serializable props (strings, numbers, plain objects).
4. **Leverage streaming with Suspense**: Wrap asynchronous Server Components in `<Suspense fallback={<Skeleton />}>` to stream UI chunks.
5. **Handle mutations via Server Actions**: Use `'use server'` functions for form submissions and database mutations.
## Commands / code examples
```tsx
// app/users/page.tsx (Server Component)
import { Suspense } from 'react';
import UserList from './UserList';
import UserListSkeleton from './UserListSkeleton';
export default async function UsersPage() {
return (
<main className="p-6">
<h1 className="text-2xl font-bold mb-4">Team Directory</h1>
<Suspense fallback={<UserListSkeleton />}>
<UserList />
</Suspense>
</main>
);
}
// app/users/UserList.tsx
async function UserList() {
const res = await fetch('https://api.example.com/users', { next: { revalidate: 60 } });
const users: Array<{ id: string; name: string }> = await res.json();
return (
<ul className="divide-y">
{users.map((user) => (
<li key={user.id} className="py-2">{user.name}</li>
))}
</ul>
);
}
```
## Common mistakes & pitfalls
- Adding `'use client'` at the root layout, effectively disabling Server Components across the app.
- Passing non-serializable values (functions, class instances, symbols) across the server-client boundary.
- Leaking private environment variables or API keys through Client Component props.
## Verification checklist
- [ ] Data-fetching components run exclusively on the server.
- [ ] `'use client'` is pushed down to leaf interactive components only.
- [ ] Async components are wrapped with `<Suspense>` boundaries.
- [ ] Sensitive backend credentials remain isolated on the server.
## Related skills
- nextjs-app-router
- react-fundamentals
- server-sent-events-sse
- web-vitals-lcp-cls-inp-optimization
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · nextboxis/library-skill-agents | 100 | MIT |
| j4flmao/agent-skills | 100 | MIT |
| claude-dev-suite/claude-dev-suite | 100 | MIT |
| chrishuffman5/domain-expert | 100 | MIT |
| Thisisjuke/skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version bd68cb5a2d1d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100react-server-components-framework
Use when building Next.js 16+ apps with React Server Components. Covers App Router, Cache Components (replacing experimental_ppr), streaming SSR, Server Actions, and React 19 patterns for server-first architecture. - 100server-components
This skill should be used when the user asks about "Server Components", "Client Components", "'use client' directive", "when to use server vs client", "RSC patterns", "component composition", "data fetching in components", or needs guidance on React Server Components architecture in Next.js. - 100react-rsc
Use when working with React Server Components — choosing between Server and Client components, designing the server/client boundary, debugging hydration mismatches, fetching data on the server, using Server Actions, optimizing initial load, or migrating from a Pages Router or… - 100frontend-react
Professional React development skill covering Next.js, React Server Components, Tailwind CSS, and the React ecosystem. Use this skill when building modern React applications, implementing Next.js features, creating UI components with shadcn/ui, or working with complex state management. - 100frontend-react
Professional React development skill covering Next.js, React Server Components, Tailwind CSS, and the React ecosystem. Use this skill when building modern React applications, implementing Next.js features, creating UI components with shadcn/ui, or working with complex state management. - 100react
Expert React assistance covering React 19, Server Components (RSC), hooks, compiler optimizations, and concurrent features. Use when building modern web user interfaces and single-page apps.