frontend-state-management
Choose the right home for every piece of frontend state — server, client, URL, form, and derived — so React/TS apps stay predictable and never store the same truth twice. Covers TanStack Query vs Zustand/Jotai/Redux/signals, normalization, colocation, and the duplication traps that cause stale UI.
Included with Vanara Pro ($10/mo) — unlocks all 206 items. See pricing →
Overview
Most "weird UI" bugs — a list that won't refresh, a badge stuck at the old count, a filter that resets on reload — are not rendering bugs. They are state-ownership bugs: the same fact lives in two places and the copies drift apart. The discipline of state management is mostly deciding where each fact lives, and then refusing to copy it anywhere else. This skill is the deep reference for that decis
What it covers
- Mental model: five kinds of state
- Rule 1 — Never duplicate server state into a client store
- Rule 2 — Derive, don't store
- Rule 3 — Put shareable state in the URL
- Rule 4 — Colocate first, lift only when shared
- Choosing a library
- Library Trade-offs
- Normalizing Entities & Deriving with Selectors