react-19
This skill should be used when the user is building, modifying, or reviewing React components or applications. It provides React 19.x development patterns and APIs that should be preferred over legacy approaches. Covers Actions, useActionState, useFormStatus, useOptimistic, use() API, Form Actions, ref as prop, Context as provider, document metadata, Server Components, Server Actions, prerender(), Activity component, useEffectEvent, cacheSignal(), and Partial Pre-rendering.
What this skill does
# React 19.x Development
This skill provides guidance on React 19.x features that may not be in LLM training data. Focus is on new APIs, patterns, and migration from older React patterns.
## When to Apply React 19 Patterns
When generating or modifying React code, always prefer React 19 patterns over legacy equivalents:
- Replace `forwardRef` wrappers with `ref` as a regular prop
- Replace `<Context.Provider>` with `<Context>` directly
- Replace manual pending/error state management with `useActionState` and form actions
- Replace manual optimistic state with `useOptimistic`
- Replace conditional rendering (`{show && <Component />}`) with `<Activity>` when state preservation matters
- Use `use()` instead of `useContext()` when context is read conditionally
- Use `useEffectEvent` to prevent unnecessary effect re-runs from non-reactive values
Consult the decision tree below to select the appropriate API. For detailed patterns, consult the relevant reference file.
## Quick API Reference
### New Hooks (React 19)
| Hook | Purpose | Import |
|------|---------|--------|
| `useActionState` | Form state + pending + error handling | `react` |
| `useFormStatus` | Read parent form's pending state | `react-dom` |
| `useOptimistic` | Optimistic UI updates | `react` |
| `use` | Read promises/context conditionally | `react` |
### New Hooks (React 19.2)
| Hook | Purpose | Import |
|------|---------|--------|
| `useEffectEvent` | Stable event handlers in effects | `react` |
### New Components (React 19.2)
| Component | Purpose |
|-----------|---------|
| `<Activity>` | Control visibility/priority of subtrees |
### Enhanced in React 19
| API | Change | Import |
|-----|--------|--------|
| `useDeferredValue` | New optional `initialValue` parameter | `react` |
### New Utilities (React 19)
| Function | Purpose | Import |
|----------|---------|--------|
| `requestFormReset` | Programmatically reset a form after action | `react-dom` |
## Decision Tree: Which API to Use?
```
Handling form submission?
├── Need pending state in child component? → useFormStatus
├── Need optimistic updates? → useOptimistic
├── Need form state + error handling? → useActionState
└── Simple async action? → useTransition with async
Reading async data?
├── In render, with Suspense? → use(promise)
└── In effect/event handler? → Regular await
Reading context conditionally?
└── After early return? → use(Context) instead of useContext
Effect needs reactive value but shouldn't re-run?
└── → useEffectEvent
Conditional rendering with state preservation?
└── → <Activity mode="visible|hidden">
```
## Core Patterns
### 1. Form Actions (replaces manual submit handlers)
```jsx
// OLD: Manual state management
function OldForm() {
const [isPending, setIsPending] = useState(false);
const [error, setError] = useState(null);
const handleSubmit = async (e) => {
e.preventDefault();
setIsPending(true);
const result = await submitData(new FormData(e.target));
setIsPending(false);
if (result.error) setError(result.error);
};
return <form onSubmit={handleSubmit}>...</form>;
}
// NEW: Form Actions with useActionState
function NewForm() {
const [error, submitAction, isPending] = useActionState(
async (prevState, formData) => {
const result = await submitData(formData);
if (result.error) return result.error;
redirect('/success');
return null;
},
null
);
return (
<form action={submitAction}>
<input name="field" />
<button disabled={isPending}>Submit</button>
{error && <p>{error}</p>}
</form>
);
}
```
### 2. ref as Prop (no more forwardRef)
```jsx
// OLD: Required forwardRef wrapper
const OldInput = forwardRef(function OldInput({ label }, ref) {
return <input ref={ref} aria-label={label} />;
});
// NEW: ref is just a prop
function NewInput({ label, ref }) {
return <input ref={ref} aria-label={label} />;
}
// Both used the same way
<NewInput ref={inputRef} label="Name" />
```
### 3. Context as Provider
```jsx
// OLD
<ThemeContext.Provider value={theme}>
{children}
</ThemeContext.Provider>
// NEW
<ThemeContext value={theme}>
{children}
</ThemeContext>
```
### 4. use() API for Conditional Context
```jsx
// useContext cannot be called after early return
function Component({ show }) {
if (!show) return null;
// const theme = useContext(ThemeContext); // ERROR!
const theme = use(ThemeContext); // OK!
return <div style={{ color: theme.color }}>...</div>;
}
```
### 5. Activity Component (React 19.2)
```jsx
// OLD: Unmounts and loses state
{isVisible && <ExpensiveComponent />}
// NEW: Preserves state, defers updates when hidden
<Activity mode={isVisible ? 'visible' : 'hidden'}>
<ExpensiveComponent />
</Activity>
```
### 6. useEffectEvent (React 19.2)
```jsx
// Problem: theme change causes reconnect
function ChatRoom({ roomId, theme }) {
useEffect(() => {
const conn = connect(roomId);
conn.on('connected', () => showNotification(theme));
return () => conn.disconnect();
}, [roomId, theme]); // theme shouldn't trigger reconnect!
}
// Solution: useEffectEvent
function ChatRoom({ roomId, theme }) {
const onConnected = useEffectEvent(() => {
showNotification(theme); // Always reads latest theme
});
useEffect(() => {
const conn = connect(roomId);
conn.on('connected', onConnected);
return () => conn.disconnect();
}, [roomId]); // Only roomId triggers reconnect
}
```
## Common Pitfalls
### useActionState
- First param receives `(previousState, formData)` - don't forget `previousState`
- Returns `[state, action, isPending]` - order matters
- Renamed from `useFormState` in React DOM
### useFormStatus
- Must be used in a component that's a child of `<form>`
- Cannot be used in the same component that renders the form
- Returns `{ pending, data, method, action }`
### useOptimistic
- Automatically reverts on error - no manual rollback needed
- Use with `startTransition` or form actions
### use()
- Only for promises created outside render (from cache, loader, etc.)
- Never create promises in render and pass to `use()`
- Works with Suspense boundaries
### ref Cleanup Functions
```jsx
// NEW: Cleanup function syntax
<input
ref={(node) => {
// Setup
node.focus();
return () => {
// Cleanup when ref changes or unmounts
};
}}
/>
// BREAKING: Implicit returns now fail TypeScript
<div ref={current => (instance = current)} /> // BAD
<div ref={current => { instance = current; }} /> // GOOD
```
### useEffectEvent
- Do NOT add to dependency array (it's stable)
- Only use for "event" logic, not to silence linter
## Migration Codemods
Available codemods for automatic migration from React 18 patterns:
```bash
npx codemod react/19/replace-forward-ref # forwardRef → ref as prop
npx codemod react/19/replace-context-provider # Context.Provider → Context
```
## References
For detailed documentation on specific topics:
- **[Actions & Forms](references/actions.md)**: useActionState, useFormStatus, useOptimistic, form actions
- **[use() API](references/use-api.md)**: Reading promises and context with use()
- **[Server Components](references/server-components.md)**: RSC, Server Actions, cacheSignal
- **[Rendering APIs](references/rendering.md)**: prerender, Activity, Partial Pre-rendering
- **[Syntax Improvements](references/improvements.md)**: ref as prop, Context provider, metadata, stylesheets, scripts
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.