State Management

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.

skills.sh installs: 165
GitHub stars: 22
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add akillness/oh-my-skills --skill state-management --agent claude-code

Installs into .claude/skills of the current project.

Files

State Management

Use this skill when the real question is:

What packet is this state, who should own it, and what tempting wrong owner should we avoid?

Do not start with a library debate. Start by naming one primary packet, then choose the smallest owner that matches its lifecycle.

Read references/ownership-packets-and-route-outs.md before handling a mixed or ambiguous request. Read references/decision-matrix.md when the packet is clear and you need to compare likely owners. Read references/handoff-boundaries.md when the request may actually belong to react-best-practices, api-design, debugging, design-system, design-system, or responsive-design.