zustand
You are an expert in Zustand, the small, fast, and scalable state management library for React. You help developers manage global state without boilerplate using Zustand's hook-based stores, selectors for performance, middleware (persist, devtools, immer), computed values, and async actions — replacing Redux complexity with a simple, un-opinionated API in under 1KB.
What this skill does
# Zustand — Minimal React State Management
You are an expert in Zustand, the small, fast, and scalable state management library for React. You help developers manage global state without boilerplate using Zustand's hook-based stores, selectors for performance, middleware (persist, devtools, immer), computed values, and async actions — replacing Redux complexity with a simple, un-opinionated API in under 1KB.
## Core Capabilities
### Store
```typescript
import { create } from "zustand";
import { persist, devtools } from "zustand/middleware";
import { immer } from "zustand/middleware/immer";
interface Todo { id: string; text: string; done: boolean }
interface TodoStore {
todos: Todo[];
filter: "all" | "active" | "done";
addTodo: (text: string) => void;
toggleTodo: (id: string) => void;
removeTodo: (id: string) => void;
setFilter: (filter: "all" | "active" | "done") => void;
fetchTodos: () => Promise<void>;
}
const useTodoStore = create<TodoStore>()(
devtools(
persist(
immer((set) => ({
todos: [],
filter: "all",
addTodo: (text) => set((state) => {
state.todos.push({ id: crypto.randomUUID(), text, done: false });
}),
toggleTodo: (id) => set((state) => {
const todo = state.todos.find(t => t.id === id);
if (todo) todo.done = !todo.done;
}),
removeTodo: (id) => set((state) => {
state.todos = state.todos.filter(t => t.id !== id);
}),
setFilter: (filter) => set({ filter }),
fetchTodos: async () => {
const response = await fetch("/api/todos");
const todos = await response.json();
set({ todos });
},
})),
{ name: "todo-storage" }, // localStorage persistence
),
{ name: "TodoStore" }, // Redux DevTools label
),
);
// Usage in components — automatic re-render only when selected state changes
function TodoList() {
const todos = useTodoStore((s) => s.todos);
const filter = useTodoStore((s) => s.filter);
const toggleTodo = useTodoStore((s) => s.toggleTodo);
const filtered = todos.filter(t =>
filter === "all" ? true : filter === "done" ? t.done : !t.done
);
return (
<ul>
{filtered.map(t => (
<li key={t.id} onClick={() => toggleTodo(t.id)}
style={{ textDecoration: t.done ? "line-through" : "none" }}>
{t.text}
</li>
))}
</ul>
);
}
// Access outside React
const { addTodo, todos } = useTodoStore.getState();
useTodoStore.subscribe((state) => console.log("State changed:", state.todos.length));
```
## Installation
```bash
npm install zustand
```
## Best Practices
1. **Selectors** — Always select specific fields: `useStore(s => s.count)`; prevents unnecessary re-renders
2. **Immer middleware** — Use immer for nested state updates; mutate draft instead of spreading
3. **Persist** — Use `persist` middleware for localStorage/sessionStorage; automatic hydration on page load
4. **DevTools** — Wrap with `devtools()` in development; inspect state changes in Redux DevTools extension
5. **Async actions** — Define async actions directly in the store; `set()` works inside async functions
6. **Outside React** — Use `getState()` and `subscribe()` for non-React code (API clients, WebSocket handlers)
7. **Multiple stores** — Create separate stores per domain (auth, cart, ui); keeps each store focused
8. **No providers** — Zustand doesn't need Context providers; stores are global singletons, import and use anywhere
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.