Create type-safe Zustand stores using the StoreBuilder utility.
npx skills add https://github.com/Cygnusfear/claude-stuff --skill superpower-zustand
Please help me install this Agent Skill. Skill: superpower-zustand Source: https://github.com/Cygnusfear/claude-stuff/tree/main/skills/superpower-zustand Command: npx skills add https://github.com/Cygnusfear/claude-stuff --skill superpower-zustand
This skill eliminates the complexity and inconsistency often found in Zustand store implementations by enforcing a standardized, type-safe StoreBuilder pattern. It ensures all stores follow best practices, saving development time and reducing debugging efforts.
const { set, createFactory } = StoreBuilder<Omit<MyStoreState, 'setValue' | 'addItem'>>( { value: 0, items: [], } );
const useMyStore = createFactory({ setValue: (v: number) => set((state) => { state.value = v; }), addItem: (item: string) => set((state) => { state.items.push(item); }), });
High-intent search queries and answers about installing and using this skill.
Use the StoreBuilder pattern to create type-safe Zustand stores by separating state from actions via Omit, initializing with StoreBuilder, and creating actions with createFactory. This enforces consistency across all stores and eliminates boilerplate while maintaining full TypeScript support.
Yes. StoreBuilder integrates Immer middleware by default, letting you write mutations directly on draft state without manual immutability patterns. Changes are automatically applied as immutable updates to your Zustand store.
StoreBuilder supports optional persistence through fine-grained configuration. Define persistence settings when initializing the store, and state automatically syncs across sessions without additional setup.
StoreBuilder exports both a hook for reactive components and get/set methods for non-reactive access. Use the hook in React components for automatic re-renders, or get/set directly when you need state outside component subscriptions.
No. StoreBuilder wraps standard Zustand patterns with a consistent interface. If you know Zustand and React, you already have the knowledge—StoreBuilder simply enforces best practices and eliminates decision-making for store structure.
Yes. Refactor existing stores by separating state from actions using Omit, then adapt them to use StoreBuilder and createFactory. The underlying Zustand behavior remains the same; you're adopting a standardized scaffolding pattern.
qazuorManage React client-side state with Zustand stores, slices, and middleware.
bxmaximumPublish and handle Bitrix events across modern and legacy APIs.
flaviogragnolatiAutomate Zustand store setup with TypeScript and middleware in React.
Gentleman-ProgrammingAutomate Zustand 5 state management patterns for React applications.
