React Server Components patterns for Next.js 16. Server vs Client boundaries, async components, data fetching, serialization rules, streaming with Suspense.
From fuse-nextjsnpx claudepluginhub fusengine/agents --plugin fuse-nextjsThis skill uses the workspace's default tool permissions.
references/rsc-patterns.mdreferences/streaming.mdDesigns and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Server Components are the default rendering model in Next.js 16 with React 19.
Before ANY implementation, use TeamCreate to spawn 3 agents:
After implementation, run fuse-ai-pilot:sniper for validation.
| 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 |
'use client' only when needed - Hooks, events, browser APIsserver-only package'use client' as deep as possiblechildren to Clientserver-only - Prevent accidental client imports of secretsPromise.all() for independent datause cache - Cache expensive server computations| Need | Reference |
|---|---|
| Server vs Client patterns | rsc-patterns.md |
| Streaming and Suspense | streaming.md |
| Data fetching in RSC | rsc-patterns.md |
| Loading states | streaming.md |