Agent skill

React Server Components Framework

by yonatangross in yonatangross/orchestkit

A skill your agent uses when building Next.js 16+ apps with React Server Components.

MITAuto-check passedDevelopment

Install React Server Components Framework

skills CLI
$ npx skills add yonatangross/orchestkit --skill react-server-components-framework -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yonatangross/orchestkit react-server-components-framework --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/react-server-components-framework .claude/skills/react-server-components-framework && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
react-server-components-framework
GitHub stars
288
Token cost
~2.7k tokens
SKILL.md length
843 words
Files
17 (incl. scripts, references)
Skills in repo
107
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when building Next.js 16+ apps with React Server Components.

  • Works in 4 steps: Streaming API Patterns - Real-time data… → Type Safety & Validation - tRPC… → Edge Computing Patterns - Global… → …
  • Building Next.js 16+ apps with React Server Components
  • SKILL.md covers Overview, Quick Reference, References and Upstream coverage (do not…, plus 6 more sections
  • Runs TypeScript scripts from its folder; calls npx

What it does

React Server Components Framework is an agent skill from yonatangross/orchestkit. Use when building Next.js 16+ apps with React Server Components. Covers App Router, Cache Components (replacing experimentalppr), streaming SSR, Server Actions, and React 19 patterns for server-first architecture.

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 20 other files, including scripts and reference files (for example `references/capability-details.md`, `references/ork-delta.md` and `references/tanstack-router-patterns.md`). Compatibility notes: Claude Code 2.1.277+.

It sits in Development. It works with React, Next.js and Turborepo. The repository describes itself as: The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install ork for stable (v9.x), or ork-alpha for the v10 line, which ships daily. The licence is MIT.

When your agent uses it

  • Building Next.js 16+ apps with React Server Components

Example prompts

  • “/react-server-components-framework”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Claude Code 2.1.277+.
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, WebSearch

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Streaming API Patterns - Real-time data patterns
  2. Type Safety & Validation - tRPC integration
  3. Edge Computing Patterns - Global deployment
  4. Performance Optimization - Core Web Vitals

What it can do on your machine

Read from SKILL.md and the folder at commit 1f8d8f3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • WebFetch
    • WebSearch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • nextjs.org
    • react.dev
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Claude Code 2.1.277+.

    From compatibility in the SKILL.md frontmatter.

Context cost

React Server Components Framework loads about 2.7k tokens when it runs, and up to ~7k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 843 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from yonatangross/orchestkit at commit 1f8d8f3, republished under its MIT licence (© yonatangross). 843 words, ~2,697 tokens.

Download SKILL.mdSave it as .claude/skills/react-server-components-framework/SKILL.md (or your agent's skills folder). This skill also uses 16 other files; get the full folder from GitHub.
name
react-server-components-framework
description
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.
allowed-tools
Read, Glob, Grep, WebFetch, WebSearch
compatibility
Claude Code 2.1.277+.
license
MIT
context
fork
agent
frontend-ui-developer
user-invocable
false
disable-model-invocation
false
metadata.category
document-asset-creation
metadata.version
1.5.0
metadata.author
OrchestKit
metadata.complexity
medium
metadata.tags
frontend, react, react-19.2, nextjs-16, server-components, streaming, cache-components, turbopack

React Server Components Framework

Overview

React Server Components (RSC) enable server-first rendering with client-side interactivity. This skill covers Next.js 16.2 LTS App Router patterns, Server Components, Server Actions, and streaming.

Next.js 16.2.6 / React 19.2.6 (security release, May 2026) — Turbopack is the default bundler (no --turbo flag needed), Server Fast Refresh is on by default, and the new cacheComponents config flag replaces the legacy experimental_ppr escape hatch. For AI-agent debugging Next.js ships Next DevTools MCP — wire npx -y next-devtools-mcp@latest into .mcp.json (it connects via the dev server's /_next/mcp endpoint) to inspect render trees and cache boundaries mid-session.

When to use this skill:

  • Building Next.js 16+ applications with the App Router
  • Designing component boundaries (Server vs Client Components)
  • Implementing data fetching with caching and revalidation
  • Creating mutations with Server Actions
  • Optimizing performance with streaming and Suspense

Quick Reference

Server vs Client Components
FeatureServer ComponentClient Component
DirectiveNone (default)'use client'
Async/awaitYesNo
HooksNoYes
Browser APIsNoYes
Database accessYesNo
Client JS bundleZeroShips to client

Key Rule: Server Components can render Client Components, but Client Components cannot directly import Server Components (use children prop instead).

Data Fetching Quick Reference

Next.js 16 Cache Components (Recommended):

tsx
import { cacheLife, cacheTag } from 'next/cache'

// Default — shared across all users (public CDN-cached)
async function CachedProducts() {
  'use cache'
  cacheLife('hours')
  cacheTag('products')
  return await db.product.findMany()
}

// Remote variant (16.2+) — always served from the edge/CDN, never rendered
// inline on the origin. Best for static product listings, marketing content.
async function MarketingHero() {
  'use cache: remote'
  cacheLife('days')
  return <Hero />
}

// Private variant (16.2+) — cached per-user session. Never shared across
// users. Use for personalized dashboards with expensive computation.
async function UserDashboard({ userId }: { userId: string }) {
  'use cache: private'
  cacheLife('minutes')
  cacheTag(`user:${userId}`)
  return await loadDashboard(userId)
}

// Invalidate cache — v16 requires a cacheLife profile as the 2nd arg
import { revalidateTag } from 'next/cache'
revalidateTag('products', 'max') // or updateTag('products') for read-your-writes

Enable via next.config.ts:

ts
import type { NextConfig } from 'next'
const config: NextConfig = {
  cacheComponents: true,  // 16.2+ — replaces experimental_ppr flag
}
export default config

Legacy Fetch Options (Next.js 15):

tsx
// Static (cached indefinitely)
await fetch(url, { cache: 'force-cache' })

// Revalidate every 60 seconds
await fetch(url, { next: { revalidate: 60 } })

// Always fresh
await fetch(url, { cache: 'no-store' })

// Tag-based revalidation
await fetch(url, { next: { tags: ['posts'] } })
Server Actions Quick Reference
tsx
'use server'

export async function createPost(formData: FormData) {
  const title = formData.get('title') as string
  const post = await db.post.create({ data: { title } })
  revalidatePath('/posts')
  redirect("/posts/" + post.id)
}
Async Params/SearchParams (Next.js 16)

Route parameters and search parameters are now Promises that must be awaited:

tsx
// app/posts/[slug]/page.tsx
export default async function PostPage({
  params,
  searchParams,
}: {
  params: Promise<{ slug: string }>
  searchParams: Promise<{ page?: string }>
}) {
  const { slug } = await params
  const { page } = await searchParams
  return <Post slug={slug} page={page} />
}

Note: Also applies to layout.tsx, generateMetadata(), and route handlers. Complete migration guide: first-party next-upgrade / vercel:next-upgrade skill. House scars: Read("references/ork-delta.md").

Dev Server (Next.js 16.2 LTS)
  • Turbopack default — next dev and next build run Turbopack without any flag. Pass --webpack only when forced (legacy plugin).
  • Server Fast Refresh — Server Components hot-reload on save without losing client state. No extra config; it's on by default in 16.2.
  • Next DevTools MCP — register npx -y next-devtools-mcp@latest in .mcp.json; it attaches to the running dev server over the /_next/mcp endpoint and exposes RSC payloads and cache boundaries to an MCP client. Designed for AI agents that need to inspect render trees mid-session without screenshotting. (There is no next-browser binary.)

References

Load on demand with Read("references/<file>"):

FileContent
ork-delta.mdHouse rules and scars: fabricated-API corrections from PR #2143, React 19 house conventions (2026-07-31 distillation)
tanstack-router-patterns.mdReact 19 features without Next.js, route-based data fetching, client-rendered app patterns
capability-details.mdKeyword and problem-mapping metadata for all 12 RSC capabilities

Upstream coverage (do not restate)

Vendor tutorials for these topics live in first-party skills and docs. This skill keeps only floors, scars, and house decisions (references/ork-delta.md).

TopicFirst-party source
Server Components fundamentals (async components, data fetching, route segment config, generateStaticParams, error handling)next-best-practices / vercel:nextjs skill; nextjs.org/docs
Client Components, 'use client', hydration, client-only renderingnext-best-practices / vercel:nextjs skill
Server/Client boundary and composition patterns, serializable propsnext-best-practices / vercel:nextjs skill; vercel-composition-patterns
Data fetching and caching (fetch cache options, revalidate, tags)next-best-practices / vercel:nextjs skill
Streaming SSR, Suspense boundaries, loading.tsx, skeleton statesvercel:nextjs skill (streaming)
Server Actions, progressive enhancement, useActionState forms, Zod validationvercel:nextjs skill (Server Actions)
Advanced routing (parallel, intercepting, route groups, dynamic and catch-all)vercel:nextjs skill (routing)
Pages Router to App Router migrationnext-upgrade / vercel:next-upgrade skill
Next.js 16 upgrade, breaking changes, codemodsnext-upgrade / vercel:next-upgrade skill
Cache Components: use cache, cacheLife, cacheTag, updateTag, PPRnext-cache-components / vercel:next-cache-components skill
React 19 core APIs (useActionState, useFormStatus, useOptimistic, use(), ref as prop)context7: /vercel/next.js + react.dev (query-docs)
RSC implementation and deployment checklistnext-best-practices skill

Show full SKILL.md (292 more words)Show less

Best Practices Summary

Component Boundaries
  • Keep Client Components at the edges (leaves) of the component tree
  • Use Server Components by default
  • Extract minimal interactive parts to Client Components
  • Pass Server Components as children to Client Components
Data Fetching
  • Fetch data in Server Components close to where it's used
  • Use parallel fetching (Promise.all) for independent data
  • Set appropriate cache and revalidate options
  • Use generateStaticParams for static routes
Performance
  • Use Suspense boundaries for streaming
  • Implement loading.tsx for instant loading states
  • Enable PPR for static/dynamic mix
  • Use route segment config to control rendering mode

Templates

  • scripts/server-component-template.tsx - Basic async Server Component with data fetching
  • scripts/client-component-template.tsx - Interactive Client Component with hooks
  • scripts/server-action-template.ts - Server Action with validation and revalidation
  • scripts/create-server-component.md - Command-style scaffold; kept as the script-invocation contract exercised by tests/skills/scripts/

Troubleshooting

ErrorFix
"You're importing a component that needs useState"Add 'use client' directive
"async/await is not valid in non-async Server Components"Add async to function declaration
"Cannot use Server Component inside Client Component"Pass Server Component as children prop
"Hydration mismatch"Use 'use client' for Date.now(), Math.random(), browser APIs
"params is not defined" or params returning PromiseAdd await before params (Next.js 16 breaking change)
"experimental_ppr is not a valid export"Use Cache Components with "use cache" directive instead
"cookies/headers is not a function"Add await before cookies() or headers() (Next.js 16)

Resources


After mastering React Server Components:

  1. Streaming API Patterns - Real-time data patterns
  2. Type Safety & Validation - tRPC integration
  3. Edge Computing Patterns - Global deployment
  4. Performance Optimization - Core Web Vitals

Capability Details

Keyword and problem-mapping metadata for each RSC capability (react-19-patterns, use-hook-suspense, optimistic-updates-async, rsc-patterns, server-actions, data-fetching, streaming-ssr, caching, cache-components, tanstack-router-patterns, async-params, nextjs-16-upgrade).

Load full capability details: Read("references/capability-details.md")

© yonatangross, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 16 other files (scripts, references) in src/skills/react-server-components-framework of yonatangross/orchestkit.

  • SKILL.md
  • examples/blog-app-example.tsx
  • references/capability-details.md
  • references/ork-delta.md
  • references/tanstack-router-patterns.md
  • rules/_sections.md
  • rules/_template.md
  • rules/rsc-cache-safety.md
  • rules/rsc-client-boundaries.md
  • rules/rsc-component-types.md
  • rules/rsc-hydration.md
  • rules/rsc-serialization.md
  • scripts/client-component-template.tsx
  • scripts/create-server-component.md
  • scripts/server-action-template.ts
  • scripts/server-component-template.tsx
  • test-cases.json

Open the folder on GitHubat commit 1f8d8f3

Compare with similar skills

React Server Components Framework next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

React Server Components Framework compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
React Server Components Framework this skillyonatangross/orchestkit288—~2.7kAutomated safety check: PassMIT
Nextjs16 Skillselophanto/EloPhanto106—~1.4kAutomated safety check: PassCustom licence
Next JS 16 Launchpadaiskillstore/marketplace430—~1.8kAutomated safety check: PassMIT
Web FrameworksMicrock/ordinary-claude-skills401—~2.3kAutomated safety check: PassMIT
Nuqstrycompai/crm11k1 repos~1.7kAutomated safety check: PassMIT
Next Best Practicesvercel-labs/openreview1.7k18 repos~1kAutomated safety check: PassNone

Similar skills

  • Nextjs16 Skills

    elophanto/EloPhanto

    Key facts and links for Next.js 16. An agent skill from elophanto/EloPhanto.

    106 GitHub stars~1.4k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Next JS 16 Launchpad

    aiskillstore/marketplace

    Next.js 16 with Turbopack, Cache Components, and proxy.ts. An agent skill from aiskillstore/marketplace.

    430 GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Web Frameworks

    Microck/ordinary-claude-skills

    Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution)…

    401 GitHub stars~2.3k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Nuqs

    trycompai/crm

    nuqs (type-safe URL query state) best practices for Next.js and other React frameworks.

    11k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed
  • Next Best Practices

    vercel-labs/openreview

    Official

    Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

    1.7k GitHub starsUsed in 18 repos~1k tokens
    DevelopmentAuto-check passed
  • Ultracite

    agustinusnathaniel/nextarter-tailwind

    Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects.

    125 GitHub starsUsed in 2 repos~1.2k tokens
    DevelopmentAuto-check passed

More from yonatangross/orchestkit

All 107 skills in this repo
  • API Design

    yonatangross/orchestkit

    API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs.

    288 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Architecture Decision Record

    yonatangross/orchestkit

    ADR templates in the Nygard format with context, decision, consequences, and alternatives.

    288 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Audit Full

    yonatangross/orchestkit

    Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.

    288 GitHub stars~3.5k tokensUpdated yesterday
    Auto-check: notes
  • Code Review Playbook

    yonatangross/orchestkit

    Structured review processes, conventional comments, language-specific checklists, and feedback templates.

    288 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Create PR

    yonatangross/orchestkit

    Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.

    288 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check: notes
  • Explore

    yonatangross/orchestkit

    Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.

    288 GitHub stars~3.9k tokensUpdated yesterday
    Auto-check: notes

Categories

Questions about React Server Components Framework

What does React Server Components Framework do?

A skill your agent uses when building Next.js 16+ apps with React Server Components. React Server Components Framework is an agent skill from yonatangross/orchestkit.js 16+ apps with React Server Components.

When should I use React Server Components Framework?

React Server Components Framework fits situations like: building Next.js 16+ apps with React Server Components.

How do I install React Server Components Framework in Claude Code?

Run `npx skills add yonatangross/orchestkit --skill react-server-components-framework -a claude-code`. Or copy the skill folder (src/skills/react-server-components-framework in yonatangross/orchestkit) into .claude/skills/react-server-components-framework in your project. Claude Code loads it when a task matches its description.

How do I install React Server Components Framework in Codex?

Run `npx skills add yonatangross/orchestkit --skill react-server-components-framework -a codex`. Or copy the skill folder (src/skills/react-server-components-framework in yonatangross/orchestkit) into .agents/skills/react-server-components-framework in your project. Codex loads it when a task matches its description.

Can I use React Server Components Framework in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yonatangross/orchestkit --skill react-server-components-framework -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/react-server-components-framework, .gemini/skills/react-server-components-framework, .github/skills/react-server-components-framework and .opencode/skills/react-server-components-framework in your project.

What does React Server Components Framework need to run?

Going by SKILL.md and its folder, React Server Components Framework needs TypeScript for the scripts in its folder and the command-line tools its instructions call (npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, WebSearch. Compatibility (from SKILL.md): Claude Code 2.1.277+..

Does React Server Components Framework access the network?

SKILL.md names 3 domains. As links in the text: nextjs.org, react.dev and github.com. This is read from the text; nothing was executed.

Is React Server Components Framework safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does React Server Components Framework use?

React Server Components Framework is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does React Server Components Framework use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.3k tokens, read only when the agent opens those files.

What are the alternatives to React Server Components Framework?

Skills that share tags, products or a category with React Server Components Framework: Nextjs16 Skills (elophanto/EloPhanto, 106 stars), Next JS 16 Launchpad (aiskillstore/marketplace, 430 stars), Web Frameworks (Microck/ordinary-claude-skills, 401 stars) and Nuqs (trycompai/crm, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains React Server Components Framework?

yonatangross (a GitHub user) maintains it in yonatangross/orchestkit, which has 288 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on October 6, 2026.

Source: yonatangross/orchestkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.