zustand-store-ts
Build Typed Zustand Stores
React teams need predictable global state without unclear store structure. This skill guides Claude, Codex, and Claude Code to create typed Zustand stores with selectors and middleware.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "zustand-store-ts" from https://skillstore.io/skills/sickn33-zustand-store-ts.md and its manifest at https://skillstore.io/api/skills/sickn33-zustand-store-ts/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 "zustand-store-ts". Request a store for project items with loading state and add item behavior.
Expected outcome:
A structured store plan with typed state, typed actions, selector recommendations, and integration notes for exports and tests.
Using "zustand-store-ts". Ask how to avoid rerenders when reading items from a Zustand store.
Expected outcome:
Guidance to select only the needed state value, avoid whole-store destructuring, and keep component subscriptions narrow.
Using "zustand-store-ts". Ask for a subscription outside React when a selected identifier changes.
Expected outcome:
A subscription approach that watches the selected identifier and runs a focused callback when that value changes.
Security Audit
SafeAll static findings were reviewed against SKILL.md. The backtick detections are Markdown inline code markers or fenced TypeScript examples, not executable shell or Ruby commands. The system reconnaissance finding is a comment about avoiding React rerenders, and no prompt injection or malicious intent was found.
Risk Factors
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/sickn33-zustand-store-ts/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-zustand-store-ts?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-zustand-store-ts?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-zustand-store-ts/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-zustand-store-ts.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
sickn33. (2026). zustand-store-ts security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-zustand-store-ts/audits/5BibTeX citation
@techreport{sickn33-sickn33-zustand-store-ts-2026,
author = {sickn33},
title = {zustand-store-ts security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-zustand-store-ts/audits/5},
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: "zustand-store-ts security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-zustand-store-ts/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-zustand-store-ts:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Create a Feature Store
Build a typed Zustand store for feature data, loading state, and actions.
Standardize Store Patterns
Apply consistent state, action, selector, and export conventions across a React codebase.
Review State Usage
Identify broad subscriptions and replace them with selectors that limit rerenders.
Try These Prompts
Create a TypeScript Zustand store for [feature name]. Include state fields, action names, and individual selectors for React components.
Design a Zustand store for [domain]. Use subscribeWithSelector, separate state and actions, and explain the exported store type.
Refactor this React state design into a typed Zustand store. Preserve behavior, split state from actions, and avoid broad subscriptions.
Design an outside-React subscription flow for this Zustand store. Subscribe to only the needed value and describe cleanup responsibilities.
Best Practices
- Define state and actions separately before combining them into the store type.
- Use selectors for each component instead of reading the entire store.
- Add tests for store actions and exported integration points.
Avoid
- Do not subscribe components to the whole store when they need one value.
- Do not mix unrelated feature domains into one broad store.
- Do not skip TypeScript interfaces for state and actions.