state-management
Manage client and server state with Zustand stores and React Query patterns.
51
Quality
55%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Securityby
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./frontend/.claude/skills/state-management/SKILL.mdState Management
Choose the right state solution for each use case.
Activation Conditions
- Managing global state
- Persisting state across navigation
- Cross-component data sharing
- Questions about Zustand vs React Query
Quick Reference
| Action | Rule |
|---|---|
| Read from store | use-zustand-selectors.md |
| Persist state | use-zustand-persist.md |
| Fetch server data | use-react-query-for-server.md |
Decision Tree
Is it server data (API response)?
├── Yes → React Query / Connect Query
│ (caching, refetching, invalidation)
└── No → Is it URL state?
├── Yes → React Router
│ (search params, path params)
└── No → Is it form state?
├── Yes → React Hook Form
│ (validation, submission)
└── No → Is it shared across components?
├── Yes → Zustand
│ (global, persisted)
└── No → useState / useReducer
(local component state)Rules
See rules/ directory for detailed guidance.
- Repository
- redpanda-data/console
- Commit
02210fa
- Last updated
- Created
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.