This forces you to name the state packet before picking a library. Instead of jumping straight to "Zustand vs Redux Toolkit," it walks you through classifying whether you're dealing with local UI toggles, shared subtree data, URL filters, form lifecycle, server cache, or actual cross-page workflow state. Then it recommends the smallest owner that fits: local state, Context, search params, TanStack Query, or only then a client store like Zustand or RTK. The real value is in the anti-pattern check that calls out common mistakes like mirroring server data into a global store or hiding shareable filters outside the URL. Best for React and Next.js projects where the team keeps reaching for heavyweight solutions when simpler ownership would work.
npx -y skills add akillness/oh-my-skills --skill state-management --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
juliusbrussee/caveman
mattpocock/skills
shadcn/improve
obra/superpowers
forrestchang/andrej-karpathy-skills
vercel-labs/skills