Skip to content
Back to skills

React Patterns Server Client Boundary

ASecurity

Decide what renders on the server versus client in React Server Components to minimize JavaScript shipped.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsjavascriptjavabashreactgitfrontend

Works with

  • cli

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add aniruddhaadak80/skills --skill react-patterns-server-client-boundary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of React Patterns Server Client Boundary?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for React Patterns Server Client Boundary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aniruddhaadak80-react-patterns-server-client-boundary/badge)](https://www.skillsdirectory.com/skills/aniruddhaadak80-react-patterns-server-client-boundary)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: react-patterns-server-client-boundary
description: "Decide what renders on the server versus client in React Server Components to minimize JavaScript shipped."
---
# Draw the server/client component boundary

> Decide what renders on the server versus client in React Server Components to minimize JavaScript shipped.

**Track:** 🎨 Frontend Engineering · **Domain:** React Patterns · **Level:** intermediate · **~30 min**

**Who this is for:** Frontend Engineers, Full-Stack Developers, Design Engineers, UI Developers

## When to Use This Skill

Decide what renders on the server versus client in React Server Components to minimize JavaScript shipped.
Use it whenever a matching task appears in conversation — the agent loads these instructions on demand.

## Steps

1. Default every component to server-rendered; add interactivity at the leaves
2. Push 'use client' down to the smallest interactive subtree (buttons, inputs)
3. Fetch data in server components; pass plain serializable props downward
4. Never import server-only secrets from a client module, even indirectly
5. Keep providers minimal: theme/auth wrappers are client, pages stay server
6. Audit bundle after each feature: any client component over 15KB needs justification

## Common Pitfalls

- One 'use client' at page level dragging the whole tree into the bundle
- Passing functions or class instances across the boundary

## Success Signals

- Client JS per route under 120KB gzipped
- Zero hydration mismatch warnings

## Commands

**Install with skills CLI**
```bash
npx skills add aniruddhaadak80/skills --skill react-patterns-server-client-boundary
```

**Install globally**
```bash
npx skills add aniruddhaadak80/skills --skill react-patterns-server-client-boundary -g
```

---

Part of [aniruddhaadak80/skills](https://github.com/aniruddhaadak80/skills) · Browse all at https://skills.sh/aniruddhaadak80/skills

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…