mcpField
Z
zustand-state

zustand-state

github.com/existential-birdsDevelopment85255 installsUpdated 11w ago
Repository

About zustand-state

zustand-state is a skill covering Zustand state management in TypeScript and React. It explains store updates, selectors, non-component access, vanilla stores, and review gates for persist and devtools middleware.

Key features

  1. 01Create and update Zustand stores
  2. 02Select state to limit rerenders
  3. 03Access and subscribe outside components
  4. 04Use vanilla stores without React
  5. 05Review persist and devtools safeguards

Use cases

  1. 01Managing state in a React application
  2. 02Selecting state for a component
  3. 03Connecting a store to external systems
  4. 04Reviewing persistence and DevTools setup

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/existential-birds/beagle --skill zustand-state

After installing, type/zustand-statein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

MIDDLEWARE.md
PATTERNS.md
TYPESCRIPT.md
references/
middleware.md
patterns.md
typescript.md

Details

From the project README

Zustand State Management

Minimal state management - no providers, minimal boilerplate.

Quick Reference

import { create } from 'zustand'

interface BearState {
  bears: number
  increase: (by: number) => void
}

const useBearStore = create<BearState>()((set) => ({
  bears: 0,
  increase: (by) => set((state) => ({ bears: state.bears + by })),
}))

// In component - select only what you need
const bears = useBearStore((state) => state.bears)
const increase = useBearStore((state) => state.increase)

State Updates

// Flat updates (auto-merged at one level)
set({ bears: 5 })
set((state) => ({ bears: state.bears + 1 }))

// Nested objects (manual spread required)
set((state) => ({
  nested: { ...state.nested, count: state.nested.count + 1 }
}))

// Replace entire state (no merge)
set({ bears: 0 }, true)

Selectors & Performance

// Good - subscribes only to bears
const bears = useBearStore((state) => state.bears)

// Bad - rerenders on any change
const state = useBearStore()

// Multiple values with useShallow (prevents rerenders with shallow comparison)
import { useShallow } from 'zustand/react/shallow'

const { bears, fish } = useBearStore(
  useShallow((state) => ({ bears: state.bears, fish: state.fish }))
)

// Array destructuring also works
const [bears, fish] = useBearStore(
  useShallow((state) => [state.bears, state.fish])
)

Access Outside Components

// Get current state (non-reactive)
const state = useBearStore.getState()

// Update state
useBearStore.setState({ bears: 5 })

// Subscribe to changes
const unsub = useBearStore.subscribe((state) => console.log(state))
unsub() // unsubscribe

Vanilla Store (No React)

import { createStore } from 'zustand/vanilla'

const store = createStore((set) => ({
  bears: 0,
  increase: (by) => set((state) => ({ bears: state.bears + by })),
}))

store.getState().bears
store.setState({ bears: 10 })
store.subscribe((state) => console.log(state))

Additional Documentation

Key Patterns

PatternWhen to Use
Single selectorOne piece of state needed
useShallowMultiple values, avoid rerenders
getState()Outside React, event handlers
subscribe()External systems, logging
Vanilla storeNon-React environments

Gates (persist and devtools)

Before merging code that uses these middlewares (see references/middleware.md for setup):

  1. persist — Pass when persisted keys are explicit (partialize or a reviewed full-state snapshot) and the JSON written to storage cannot include auth tokens, API keys, or other secrets.
  2. devtools in shipped bundles — Pass when DevTools runs only in development (env gate), or you leave a one-line note in the PR explaining why it stays enabled in production.

Comments

Markdown supported