state-management-expert

Guide React state architecture decisions across Redux Toolkit, Zustand, Jotai, TanStack Query, and Context API.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/VanhPoker/VietNamLookmaxing --skill state-management-expert-vanhpoker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: state-management-expert
Source: https://github.com/VanhPoker/VietNamLookmaxing/tree/main/.agent/skills/state-management-expert
Command: npx skills add https://github.com/VanhPoker/VietNamLookmaxing --skill state-management-expert-vanhpoker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams struggle to design and enforce scalable, maintainable state architectures in React applications. It provides guidance on when to use Redux Toolkit, Zustand, Jotai, TanStack Query, or Context API to manage server and UI state.

Core Features & Use Cases

  • Guidance for architecture decisions across large React apps
  • Patterns for global UI state, server state, and derived data
  • Real-world scenarios such as onboarding flows, data-heavy dashboards, and form-heavy interfaces

Quick Start

Choose a state pattern and implement it across a sample app using Redux Toolkit, Zustand, Jotai, TanStack Query, or Context API.

Frequently Asked Questions about state-management-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to manage React state for a complex application?

The best way to manage React state depends on your architecture: Redux Toolkit for complex global state, Zustand for lightweight stores, Jotai for atomic state, TanStack Query for server state, and Context API for low-frequency UI updates.

How do I choose between Redux Toolkit and Zustand for React state management?

Choose Redux Toolkit for large-scale applications requiring strict structure and middleware, and Zustand for minimal boilerplate and flexible global UI state without providers, ensuring maintainable state logic.

When do I need TanStack Query instead of Context API for state management?

You need TanStack Query for managing server state, caching, and data-fetching patterns, whereas Context API is suited for sharing low-frequency global UI state across components without triggering re-render bottlenecks.

How do I design scalable React state architecture for data-heavy dashboards?

Design scalable React state for data-heavy dashboards by combining TanStack Query for server state and derived data, Jotai for atomic derived values, and Zustand for UI state to enforce performance and maintainability.

Does Jotai work with Redux Toolkit for managing global UI state and server state?

Yes, Jotai works with Redux Toolkit by separating concerns: use Jotai for atomic, fine-grained UI state and Redux Toolkit for broader global architecture, applying integration guidelines to maintain state boundaries.

What are the limitations of using Context API for React state management?

Context API limitations include performance considerations like unnecessary re-renders when state updates, making it unsuitable for high-frequency changes in complex applications compared to Zustand or Jotai.