MCPInstall

zustand

Zustand state management best practices for React applications. Use when writing, reviewing, or refactoring Zustand stores to ensure optimal performance and maintainability. Triggers on tasks involving state management, stores, selectors, re-renders, and Zustand patterns.

Installs
448
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/pproenca/dot-skills --skill zustand
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads zustand automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Community Zustand Best Practices

Comprehensive performance and architecture guide for Zustand state management in React applications. Contains 43 rules across 8 categories, prioritized by impact from critical (store architecture, selector optimization) to incremental (advanced patterns).

When to Apply

Reference these guidelines when:

  • Creating new Zustand stores
  • Optimizing re-render performance with selectors
  • Implementing persistence or middleware
  • Integrating Zustand with SSR/Next.js
  • Reviewing code for state management patterns

Rule Categories by Priority

PriorityCategoryImpactPrefix
1Store ArchitectureCRITICALstore-
2Selector OptimizationCRITICALselect-
3Re-render PreventionHIGHrender-
4State UpdatesMEDIUM-HIGHupdate-
5Middleware ConfigurationMEDIUMmw-
6SSR and HydrationMEDIUMssr-
7TypeScript PatternsLOW-MEDIUMts-
8Advanced PatternsLOWadv-

Quick Reference

1. Store Architecture (CRITICAL)

  • store-multiple-stores - Use multiple small stores instead of one monolithic store
  • store-separate-actions - Separate actions from state in dedicated namespace
  • store-event-naming - Name actions as events not setters
  • store-colocate-logic - Colocate actions with the state they modify
  • store-avoid-derived-state - Derive computed values instead of storing them
  • store-domain-boundaries - Organize stores by feature domain

2. Selector Optimization (CRITICAL)

  • select-always-use - Always use selectors never subscribe to entire store
  • select-atomic-picks - Use atomic selectors for single values
  • select-stable-returns - Ensure selectors return stable references
  • select-custom-hooks - Export custom hooks not raw store
  • select-auto-generate - Use auto-generated selectors for large stores
  • select-memoize-computed - Memoize expensive computed selectors
  • select-avoid-inline - Define selectors outside components

3. Re-render Prevention (HIGH)

  • render-use-shallow - Use useShallow for multi-property selections
  • render-equality-fn - Provide custom equality functions when needed
  • render-memo-children - Memo children affected by parent store updates
  • render-subscribe-external - Use subscribe for non-React consumers
  • render-avoid-object-returns - Avoid returning new objects from selectors
  • render-split-components - Split components to minimize subscription scope

4. State Updates (MEDIUM-HIGH)

  • update-functional-set - Use functional form when updating based on previous state
  • update-immutable - Never mutate state directly
  • update-shallow-merge - Understand set() shallow merge behavior
  • update-async-actions - Handle async actions with loading and error states
  • update-batch-updates - Batch related updates in single set call

5. Middleware Configuration (MEDIUM)

  • mw-devtools-actions - Name actions for DevTools debugging
  • mw-persist-partialize - Use partialize for selective persistence
  • mw-persist-migration - Version and migrate persisted state
  • mw-immer-nested - Use immer for deeply nested state updates
  • mw-combine-order - Apply middlewares in correct order
  • mw-slice-middleware - Apply middleware at combined store level

6. SSR and Hydration (MEDIUM)

  • ssr-skip-hydration - Use skipHydration in SSR contexts
  • ssr-manual-rehydrate - Manually rehydrate on client mount
  • ssr-hydration-hook - Use custom hook to prevent hydration mismatch
  • ssr-check-window - Guard browser APIs with typeof window check

7. TypeScript Patterns (LOW-MEDIUM)

  • ts-state-creator - Use StateCreator for slice typing
  • ts-middleware-inference - Preserve type inference with middleware
  • ts-separate-types - Separate state and actions interfaces
  • ts-generic-selectors - Type selectors for reusability
  • ts-bound-store - Type combined stores correctly

8. Advanced Patterns (LOW)

  • adv-context-stores - Combine Zustand with React Context for dependency injection
  • adv-transient-updates - Use subscribe for transient updates
  • adv-computed-getters - Implement computed state with getters
  • adv-third-party-integration - Integrate with React Query and SWR

How to Use

Read individual reference files for detailed explanations and code examples:

  • Section definitions - Category structure and impact levels
  • Rule template - Template for adding new rules

Reference Files

FileDescription
references/_sections.mdCategory definitions and ordering
assets/templates/_template.mdTemplate for new rules
metadata.jsonVersion and reference information

FAQ

What does the zustand skill do?

Zustand state management best practices for React applications. Use when writing, reviewing, or refactoring Zustand stores to ensure optimal performance and maintainability. Triggers on tasks involving state management, stores, selectors, re-renders, and Zustand patterns.

How do I install zustand?

Run npx skills add https://github.com/pproenca/dot-skills --skill zustand in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/zustand/ (personal) or .claude/skills/zustand/ (project).

Which AI agents can use zustand?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is zustand safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains zustand?

It is published by pproenca in pproenca/dot-skills. It has 448 recorded installs.

More from pproenca/dot-skills

View all →

zod

pproenca/dot-skills

Zod schema validation best practices for type safety, parsing, and error handling. This skill should be used when defining z.object schemas, using z.string validations, safeParse, or z.infer. This skill does NOT cover React Hook Form integration patterns (use react-hook-form skill) or OpenAPI client generation (use orval skill).

Frontend & Design7.1K installs

vitest

pproenca/dot-skills

Vitest testing framework patterns for test setup, async testing, mocking with vi., snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.

Testing & QA6.2K installs

react-hook-form

pproenca/dot-skills

React Hook Form performance optimization for client-side form validation using useForm, useWatch, useController, useFieldArray, the subscribe() API, and the Watch / FormStateSubscribe / FieldArray render-prop components. Covers RHF 7.82 additions including resetDefaultValues() and the disabled field-array option. This skill should be used when building client-side controlled forms with React Hook Form library. This skill does NOT cover React 19 Server Actions, useActionState, or server-side form handling (use react-19 skill for those).

emilkowal-animations

pproenca/dot-skills

Emil Kowalski's animation best practices for web interfaces. Use when writing, reviewing, or implementing animations in React, CSS, or Framer Motion. Triggers on tasks involving transitions, easing, gestures, toasts, drawers, or motion.

Frontend & Design2.8K installs

nuqs

pproenca/dot-skills

nuqs (type-safe URL query state) best practices for Next.js and other React frameworks. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, limitUrlUpdates, Standard Schema, NuqsAdapter, or Next.js routing with state.

Frontend & Design2.3K installs

clean-architecture

pproenca/dot-skills

Clean Architecture principles and best practices from Robert C. Martin's book. This skill should be used when designing software systems, reviewing code structure, or refactoring applications to achieve better separation of concerns. Triggers on tasks involving layers, boundaries, dependency direction, entities, use cases, or system architecture.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.