zustand-state

zustand-state is a skill for Claude Code, Codex from recca0120/code-quest. It costs 44 tokens per session (1,220 once invoked), scanned A, original, MIT.

A guide to managing shared application data with Zustand, a small state-management library for React. It covers stores, selectors, middleware, and splitting large stores into slices.

In plain words
What is it for?
Use it when creating or changing Zustand stores, structuring large stores, choosing selectors or middleware, handling socket-driven state, or testing stores.
Why use it?
It provides patterns for organizing shared state and limiting unnecessary component updates. It also explains how to connect state to socket events and test it.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/recca0120/code-quest/zustand-state
Any agent
npx skills add recca0120/code-quest --skill zustand-state
Clone the repo
git clone --depth 1 https://github.com/recca0120/code-quest

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for zustand-state

README.md
[![agentmods](https://agentmods.dev/badge/skills/recca0120/code-quest/zustand-state.svg)](https://agentmods.dev/skills/recca0120/code-quest/zustand-state)
Your own site
<a href="https://agentmods.dev/skills/recca0120/code-quest/zustand-state"><img src="https://agentmods.dev/badge/skills/recca0120/code-quest/zustand-state.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,220 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.01220
Opus 5 $0.00022 $0.00610
Sonnet 5 $0.00009 $0.00244
Haiku 4.5 $0.00004 $0.00122

Measured 5d ago against content hash 435b9d8f2a7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

zustand-state scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/zustand-state/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Zustand State Management

Store Creation

Prefer create for React-bound stores. Use createStore (vanilla) only when sharing state outside React (e.g., initializing from a socket listener module).

// stores/useCounterStore.ts
import { create } from 'zustand';
import { devtools, immer } from 'zustand/middleware';

interface CounterState {
  count: number;
  increment: () => void;
}

export const useCounterStore = create<CounterState>()(
  devtools(
    immer((set) => ({
      count: 0,
      increment: () => set((state) => { state.count += 1; }),
    })),
    { name: 'CounterStore' }
  )
);

Slice Pattern (Large Stores)

Split domains into slices; apply middleware only at the root.

// stores/slices/chatSlice.ts
import { StateCreator } from 'zustand';
import { RootStore } from '../useRootStore';

export interface ChatSlice {
  messages: string[];
  addMessage: (msg: string) => void;
}

export const createChatSlice: StateCreator<RootStore, [['zustand/immer', never]], [], ChatSlice> = (set) => ({
  messages: [],
  addMessage: (msg) => set((state) => { state.messages.push(msg); }),
});

// stores/useRootStore.ts
export type RootStore = ChatSlice & OtherSlice;

export const useRootStore = create<RootStore>()(
  devtools(immer((...a) => ({ ...createChatSlice(...a), ...createOtherSlice(...a) })))
);

Selectors and Re-render Optimization

Subscribe to the minimal shape needed. Use useShallow for object/array selections; use atomic selectors for primitives.

// Primitive — no useShallow needed
const count = useCounterStore((s) => s.count);

// Multiple fields — use useShallow to avoid identity churn
import { useShallow } from 'zustand/react/shallow';
const { name, role } = useUserStore(useShallow((s) => ({ name: s.name, role: s.role })));

// Stable action reference — select once outside render or memoize
const addMessage = useRootStore((s) => s.addMessage);

Middleware Stack Order

devtools( persist( subscribeWithSelector( immer( ... ) ) ) )

Read the full file on GitHub · 159 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 159 lines · 44 tokens per session scan A 435b9d8f2a7f

Subscribe to this mod's changes

zustand-state is a skill published in the GitHub repository recca0120/code-quest (11 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,220 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

v8-jit

V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…

vercel/next.js · 88 tokens

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

material-ui-tailwind

Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.

mui/material-ui · 67 tokens

verify

Use when you want to validate changes before committing, or when you need to check all React contribution requirements.

react/react · 23 tokens

r3f-best-practices

React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.

zebbern/claude-code-guide · 74 tokens

git-safety

Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.

tamagui/tamagui · 0 tokens