# React Server Components

> Reviews React Server/Client Component boundaries against Next.js and React docs. Use when auditing `'use client'` placement or splitting components for proper RSC behaviour.

- Skill: `ryoppippi/react-server-components` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ryoppippi/react-server-components`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ryoppippi/react-server-components/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: ryoppippi (https://skillmd.com/u/ryoppippi)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ryoppippi/react-server-components

---


<!--
Example prompts:
  /react-server-components
  /react-server-components scope=src/app/
  /react-server-components fix=false
-->

Arguments:

- scope: what to analyse (default: your current changes). Examples: "diff to main", "PR #123", "src/app/", "whole codebase"
- fix: whether to apply fixes (default: true). Set to false to only propose changes.

Steps:

1. Read:
   - https://react.dev/reference/rsc/server-components
   - https://nextjs.org/docs/app/building-your-application/rendering/composition-patterns
2. Analyse the specified scope for Server/Client Component anti-patterns
3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.