Programowanie · Budowanie i kod
react-state
/react-state
Obsługuje zarządzanie stanem w React za pomocą Zustand v5: stan globalny, store'y, persist i stan po stronie klienta.
Dla kogo
- Autor
- fusengine ↗
- Repozytorium
- agents ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.10.2026
Ocena i bezpieczeństwo
90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
- Pliki w paczce
- 11
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Przestarzałość
Brak sygnałów. Repozytorium zmienione 12.10.2026, bez odwołań do wycofanych modeli i API.
Licencja
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Obsługuje zarządzanie stanem w React za pomocą Zustand v5: stan globalny, store'y, persist i stan po stronie klienta.
Oryginalny opis (EN)
Zustand v5 state management for React. Use when implementing global state, stores, persist, or client-side state.
Jak działa
- Agent Workflow (MANDATORY)
- Overview
- Critical Rules
- SOLID Architecture
- Key Concepts
- Reference Guide
- Best Practices
- Forbidden Patterns
Sekcje z nagłówków SKILL.md, w oryginale · 130 linii, 643 słów
Podgląd SKILL.md
---
name: react-state
description: Zustand v5 state management for React. Use when implementing global state, stores, persist, or client-side state.
versions:
zustand: 5.0
react: 19
user-invocable: true
references: references/installation.md, references/store-patterns.md, references/middleware.md, references/typescript.md, references/slices.md, references/auto-selectors.md, references/reset-state.md, references/subscribe-api.md, references/testing.md, references/migration-v5.md
related-skills: react-19, react-forms, solid-react
---
<objective>
Implements Zustand v5 global state management for React applications: the v5 currying syntax (`create<State>()((set) => ({...}))`), the selector pattern (`useStore((s) => s.field)`), `useShallow` for array/object selectors to prevent unnecessary re-renders, and middleware composition (devtools → persist → immer, order-sensitive for TypeScript).
Covers separating stores by domain (auth, cart, ui, theme) rather than one giant store, SOLID file organization (`store.ts`, `store.interface.ts`, `use-store.ts`), and forbidden patterns (persisting auth tokens, v4 syntax, skipping `useShallow`). This is the plain-React variant of Zustand (no App Router request-isolation concerns) — for Next.js App Router see nextjs-zustand, and for server state use TanStack Query instead of this skill.
</objective>
# Zustand for React
Minimal, scalable state management with React 18+ useSyncExternalStore.
## Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`:
1. **fuse-ai-pilot:explore-codebase** - Analyze existing stores and state patterns
2. **fuse-ai-pilot:research-expert** - Verify latest Zustand v5 docs via Context7/Exa
3. **mcp__context7__query-docs** - Check middleware and TypeScript patterns
After implementation, run **fuse-ai-pilot:sniper** for validation.
---
## Overview
### When to Use
- Managing global state in React applications
- Need state shared across components
- Persisting state to localStorage/sessionStorage
- Building UI state (modals, sidebars, theme, cart)
- Replacing React Context for complex state
### Why Zustand v5
| Feature | Benefit |
|---------|---------|
| Minimal API | Simple create() function, no boilerplate |
| React 18 native | useSyncExternalStore, no shims needed |
| TypeScript first | Full inference with currying pattern |
| Middleware stack | devtools, persist, immer composable |
| Bundle size | ~2KB gzipped, smallest state library |
| No providers | Direct store access, no Context wrapper |
---
## Critical Rules
1. **useShallow for arrays/objects** - Prevent unnecessary re-renders
2. **Currying syntax v5** - `create<State>()((set) => ({...}))`
3. **SOLID paths** - Stores in `modules/[feature]/src/stores/`
4. **Separate stores** - One store per domain (auth, cart, ui, theme)
5. **Server state elsewhere** - Use TanStack Query for server state
---
## SOLID Architecture
### Module Structure
Stores organized by feature module:
- `modules/cores/stores/` - Shared stores (theme, ui)
- `modules/auth/src/stores/` - Auth state
- `modules/cart/src/stores/` - Cart state
- `modules/[feature]/src/interfaces/` - Store types
### File Organization
| File | Purpose |
|------|---------|
| `store.ts` | Store creation with create() (max 40 lines, owner rule) |
| `store.interface.ts` | TypeScript interfaces |
| `use-store.ts` | Custom hook with selector |
---
## Key Concepts
### Store Creation (v5 Syntax)
Double parentheses required for TypeScript inference. Currying pattern ensures full type safety.
### Middleware Composition
Stack middlewares: devtools -> persist -> immer. Order matters for TypeScript types.
### Selector Pattern
Always use `useStore((s) => s.field)` for performance. Use `useShallow` for array/object selectors.
---
## Reference Guide
| Need | Reference |
|------|-----------|
| Initial setup | [installation.md](references/installation.md) |
| Store patterns | [store-patterns.md](references/store-patterns.md) |
| Middleware | [middleware.md](references/middleware.md) |
| TypeScript | [typescript.md](references/typescript.md) |
| Slices pattern | [slices.md](references/slices.md) |
| Auto selectors | [auto-selectors.md](references/auto-selectors.md) |
| Reset state | [reset-state.md](references/reset-state.md) |
| Subscribe API | [subscribe-api.md](references/subscribe-api.md) |
| Testing | [testing.md](references/testing.md) |
| Migration v4→v5 | [migration-v5.md](references/migration-v5.md) |
---
## Best Practices
1. **Selector pattern** - Always use `useStore((s) => s.field)` for performance
2. **useShallow** - Wrap array/object selectors to prevent re-renders
3. **Separate stores** - One store per domain (auth, cart, ui, theme)
4. **Server data elsewhere** - Use TanStack Query for server state
5. **DevTools in dev only** - Wrap devtools in process.env check
6. **Partialize persist** - Only persist necessary fields, never tokens
---
## Forbidden Patterns
| Pattern | Reason | Alternative |
|---------|--------|-------------|
| Persisting auth tokens | Security vulnerability | httpOnly cookies |
| Without useShallow on objects | Excessive re-renders | `useShallow(selector)` |
| v4 syntax | TypeScript inference broken | v5 currying `create<T>()()` |
| Giant monolithic store | Hard to maintain | Slices or separate stores |
Pliki w paczce (11)
- SKILL.md 5 KB
- references/auto-selectors.md 4 KB
- references/installation.md 2 KB
- references/middleware.md 5 KB
- references/migration-v5.md 4 KB
- references/reset-state.md 5 KB
- references/slices.md 5 KB
- references/store-patterns.md 5 KB
- references/subscribe-api.md 5 KB
- references/testing.md 5 KB
- references/typescript.md 6 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · fusengine/agents | 90 | MIT |
| jelvodev/yaap | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki f9758c7610eb (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90nextjs-zustand
Wdraża stan globalny, magazyny, persist i hydrację w komponentach klienckich Next.js 16 App Router z Zustand v5. - 100react-state-management
Pomaga wybrać i wdrożyć lokalny, globalny i serwerowy stan w React z Context, Zustand, Redux i React Query. - 100zustand
Opisuje zarządzanie stanem w React przez Zustand: store, akcje i trwałość, dla prostego stanu globalnego. - 100react-native-state-management
Wdraża lokalny i globalny stan w React Native z Context, Zustand i Redux Toolkit oraz pomaga wybrać rozwiązanie. - 100react-state-management
Pomaga zaprojektować współdzielony stan klienta w React, porównując Context API, Zustand i Redux Toolkit. - 100state-management
Stosuje wzorce React Query i Zustand do pobierania danych, cache'owania, mutacji i stanu po stronie klienta.