Covers separating stores by domain (auth, cart, ui, theme) rather than one giant store, SOLID file organization (store.ts, store.interface.ts, use-store.ts), and forbidden patterns (persisting auth tokens, v4 syntax, skipping useShallow). This is the plain-React variant of Zustand (no App Router request-isolation concerns) — for Next.js App Router see nextjs-zustand, and for server state use TanStack Query instead of this skill.
Zustand for React
Minimal, scalable state management with React 18+ useSyncExternalStore.
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Analyze existing stores and state patterns
- fuse-ai-pilot:research-expert - Verify latest Zustand v5 docs via Context7/Exa
- mcp__context7__query-docs - Check middleware and TypeScript patterns
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
When to Use
- Managing global state in React applications
- Need state shared across components
- Persisting state to localStorage/sessionStorage
- Building UI state (modals, sidebars, theme, cart)
- Replacing React Context for complex state
Why Zustand v5
| Feature |
Benefit |
| Minimal API |
Simple create() function, no boilerplate |
| React 18 native |
useSyncExternalStore, no shims needed |
| TypeScript first |
Full inference with currying pattern |
| Middleware stack |
devtools, persist, immer composable |
| Bundle size |
~2KB gzipped, smallest state library |
| No providers |
Direct store access, no Context wrapper |
Critical Rules
- useShallow for arrays/objects - Prevent unnecessary re-renders
- Currying syntax v5 -
create<State>()((set) => ({...}))
- SOLID paths - Stores in
modules/[feature]/src/stores/
- Separate stores - One store per domain (auth, cart, ui, theme)
- Server state elsewhere - Use TanStack Query for server state
SOLID Architecture
Module Structure
Stores organized by feature module:
modules/cores/stores/ - Shared stores (theme, ui)
modules/auth/src/stores/ - Auth state
modules/cart/src/stores/ - Cart state
modules/[feature]/src/interfaces/ - Store types
File Organization
| File |
Purpose |
Max Lines |
store.ts |
Store creation with create() |
50 |
store.interface.ts |
TypeScript interfaces |
30 |
use-store.ts |
Custom hook with selector |
20 |
Key Concepts
Store Creation (v5 Syntax)
Double parentheses required for TypeScript inference. Currying pattern ensures full type safety.
Middleware Composition
Stack middlewares: devtools -> persist -> immer. Order matters for TypeScript types.
Selector Pattern
Always use useStore((s) => s.field) for performance. Use useShallow for array/object selectors.
Reference Guide
| Need |
Reference |
| Initial setup |
installation.md |
| Store patterns |
store-patterns.md |
| Middleware |
middleware.md |
| TypeScript |
typescript.md |
| Slices pattern |
slices.md |
| Auto selectors |
auto-selectors.md |
| Reset state |
reset-state.md |
| Subscribe API |
subscribe-api.md |
| Testing |
testing.md |
| Migration v4→v5 |
migration-v5.md |
Best Practices
- Selector pattern - Always use
useStore((s) => s.field) for performance
- useShallow - Wrap array/object selectors to prevent re-renders
- Separate stores - One store per domain (auth, cart, ui, theme)
- Server data elsewhere - Use TanStack Query for server state
- DevTools in dev only - Wrap devtools in process.env check
- Partialize persist - Only persist necessary fields, never tokens
Forbidden Patterns
| Pattern |
Reason |
Alternative |
| Persisting auth tokens |
Security vulnerability |
httpOnly cookies |
| Without useShallow on objects |
Excessive re-renders |
useShallow(selector) |
| v4 syntax |
TypeScript inference broken |
v5 currying create<T>()() |
| Giant monolithic store |
Hard to maintain |
Slices or separate stores |
1---2name: react-state3description: Zustand v5 state management for React. Use when implementing global state, stores, persist, or client-side state.4versions:5 zustand: 5.06 react: 197user-invocable: true8references: references/installation.md, references/store-patterns.md, references/middleware.md, references/typescript.md, references/slices.md, references/auto-selectors.md, references/reset-state.md, references/subscribe-api.md, references/testing.md, references/migration-v5.md9related-skills: react-19, react-forms, solid-react10metadata:11 source: https://skillmd.com/skills/fusengine/react-state12---1314<objective>15Implements Zustand v5 global state management for React applications: the v5 currying syntax (`create<State>()((set) => ({...}))`), the selector pattern (`useStore((s) => s.field)`), `useShallow` for array/object selectors to prevent unnecessary re-renders, and middleware composition (devtools → persist → immer, order-sensitive for TypeScript).1617Covers separating stores by domain (auth, cart, ui, theme) rather than one giant store, SOLID file organization (`store.ts`, `store.interface.ts`, `use-store.ts`), and forbidden patterns (persisting auth tokens, v4 syntax, skipping `useShallow`). This is the plain-React variant of Zustand (no App Router request-isolation concerns) — for Next.js App Router see nextjs-zustand, and for server state use TanStack Query instead of this skill.18</objective>1920# Zustand for React2122Minimal, scalable state management with React 18+ useSyncExternalStore.2324## Agent Workflow (MANDATORY)2526Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`:27281. **fuse-ai-pilot:explore-codebase** - Analyze existing stores and state patterns292. **fuse-ai-pilot:research-expert** - Verify latest Zustand v5 docs via Context7/Exa303. **mcp__context7__query-docs** - Check middleware and TypeScript patterns3132After implementation, run **fuse-ai-pilot:sniper** for validation.3334---3536## Overview3738### When to Use3940- Managing global state in React applications41- Need state shared across components42- Persisting state to localStorage/sessionStorage43- Building UI state (modals, sidebars, theme, cart)44- Replacing React Context for complex state4546### Why Zustand v54748| Feature | Benefit |49|---------|---------|50| Minimal API | Simple create() function, no boilerplate |51| React 18 native | useSyncExternalStore, no shims needed |52| TypeScript first | Full inference with currying pattern |53| Middleware stack | devtools, persist, immer composable |54| Bundle size | ~2KB gzipped, smallest state library |55| No providers | Direct store access, no Context wrapper |5657---5859## Critical Rules60611. **useShallow for arrays/objects** - Prevent unnecessary re-renders622. **Currying syntax v5** - `create<State>()((set) => ({...}))`633. **SOLID paths** - Stores in `modules/[feature]/src/stores/`644. **Separate stores** - One store per domain (auth, cart, ui, theme)655. **Server state elsewhere** - Use TanStack Query for server state6667---6869## SOLID Architecture7071### Module Structure7273Stores organized by feature module:7475- `modules/cores/stores/` - Shared stores (theme, ui)76- `modules/auth/src/stores/` - Auth state77- `modules/cart/src/stores/` - Cart state78- `modules/[feature]/src/interfaces/` - Store types7980### File Organization8182| File | Purpose | Max Lines |83|------|---------|-----------|84| `store.ts` | Store creation with create() | 50 |85| `store.interface.ts` | TypeScript interfaces | 30 |86| `use-store.ts` | Custom hook with selector | 20 |8788---8990## Key Concepts9192### Store Creation (v5 Syntax)9394Double parentheses required for TypeScript inference. Currying pattern ensures full type safety.9596### Middleware Composition9798Stack middlewares: devtools -> persist -> immer. Order matters for TypeScript types.99100### Selector Pattern101102Always use `useStore((s) => s.field)` for performance. Use `useShallow` for array/object selectors.103104---105106## Reference Guide107108| Need | Reference |109|------|-----------|110| Initial setup | [installation.md](references/installation.md) |111| Store patterns | [store-patterns.md](references/store-patterns.md) |112| Middleware | [middleware.md](references/middleware.md) |113| TypeScript | [typescript.md](references/typescript.md) |114| Slices pattern | [slices.md](references/slices.md) |115| Auto selectors | [auto-selectors.md](references/auto-selectors.md) |116| Reset state | [reset-state.md](references/reset-state.md) |117| Subscribe API | [subscribe-api.md](references/subscribe-api.md) |118| Testing | [testing.md](references/testing.md) |119| Migration v4→v5 | [migration-v5.md](references/migration-v5.md) |120121---122123## Best Practices1241251. **Selector pattern** - Always use `useStore((s) => s.field)` for performance1262. **useShallow** - Wrap array/object selectors to prevent re-renders1273. **Separate stores** - One store per domain (auth, cart, ui, theme)1284. **Server data elsewhere** - Use TanStack Query for server state1295. **DevTools in dev only** - Wrap devtools in process.env check1306. **Partialize persist** - Only persist necessary fields, never tokens131132---133134## Forbidden Patterns135136| Pattern | Reason | Alternative |137|---------|--------|-------------|138| Persisting auth tokens | Security vulnerability | httpOnly cookies |139| Without useShallow on objects | Excessive re-renders | `useShallow(selector)` |140| v4 syntax | TypeScript inference broken | v5 currying `create<T>()()` |141| Giant monolithic store | Hard to maintain | Slices or separate stores |