react-state-management
Choose React State Management Patterns
React teams often mix local, global, and server state without clear boundaries. This skill helps apply Redux Toolkit, Zustand, Jotai, and React Query patterns.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "react-state-management" from https://skillstore.io/skills/wshobson-react-state-management.md and its manifest at https://skillstore.io/api/skills/wshobson-react-state-management/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "react-state-management". I need shared user and cart state in a medium React app.
Expected outcome:
Use Zustand slices for client state if the logic is simple. Keep selectors narrow, persist only needed fields, and avoid copying server responses.
Using "react-state-management". Our dashboard fetches user lists and supports edits.
Expected outcome:
Use React Query for lists, details, mutations, optimistic updates, and rollback. Keep UI flags such as sidebar state in a small client store.
Using "react-state-management". We have older Redux reducers and action creators.
Expected outcome:
Migrate feature by feature to Redux Toolkit. Add typed hooks, replace boilerplate reducers with slices, and move remote data to server-state tools.
Security Audit
SafeI reviewed SKILL.md and found no executable installer code, prompt injection, or malicious intent. The static findings are false positives from Markdown fences, TypeScript examples, relative API calls, and public documentation links.
Risk Factors
⚙️ External commands (19)
🌐 Network access (6)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/wshobson-react-state-management/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/wshobson-react-state-management?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/wshobson-react-state-management?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wshobson-react-state-management/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/wshobson-react-state-management.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
wshobson. (2026). react-state-management security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wshobson-react-state-management/audits/8BibTeX citation
@techreport{wshobson-wshobson-react-state-management-2026,
author = {wshobson},
title = {react-state-management security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/wshobson-react-state-management/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "react-state-management security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "wshobson"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/wshobson-react-state-management/audits/8"
identifiers:
- type: other
value: "skillstore:wshobson-react-state-management:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
wshobson-react-state-management
2026-08-21
sickn33-react-state-management
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Select a state library
Compare Redux Toolkit, Zustand, Jotai, and React Query for a new React application.
Set team boundaries
Define which data belongs in component state, global client state, and server-state caching.
Modernize old Redux code
Plan a migration from legacy reducers and action creators to Redux Toolkit patterns.
Try These Prompts
Use this skill to recommend a React state management approach for my app. My app size is [size], shared state is [state], and server data needs are [needs].
Use this skill to outline a TypeScript state store for [feature]. Include state shape, actions, selectors, and where persistence should apply.
Use this skill to review my React feature. Identify what should use React Query, what should stay local, and what needs global client state.
Use this skill to create a phased migration plan from legacy Redux to Redux Toolkit for [application area]. Preserve behavior and reduce rerenders.
Best Practices
- Keep state close to the components that use it.
- Use selectors to limit rerenders from shared stores.
- Separate server-state caching from client-only UI state.
Avoid
- Do not put every field into global state by default.
- Do not duplicate server data in a client store.
- Do not store derived values that can be computed from existing state.