zustand · pedronauck — Claude Code skill: Zustand store patterns

What zustand does

The skill hands the agent a set of rules for Zustand in your project. Stores stay domain-specific, large ones get split into slices, and selector hooks are exported for each state slice instead of subscribing to the whole store. A template shows the state interface with actions grouped in an actions object.

For production stores it recommends stacking middleware in one order: devtools, then persist, then immer. Persistence is narrowed with partialize so only the fields you pick end up in storage. The skill also draws a line between client state and server state, pointing the latter at TanStack Query.

The agent can only Read, Grep and Glob — it inspects your code and suggests changes, but never edits files itself. So don't expect it to rewrite your stores on its own. Deeper examples and anti-patterns live in references/patterns.md, and the checklist ends with pnpm run typecheck and pnpm run test.