Skills superpower-zustand

📦

superpower-zustand

Name: superpower-zustand
Author: Cygnusfear

Content revision r1 Safe ⚙️ External commands🌐 Network access

Build Standard Zustand Stores

Zustand stores often become inconsistent when actions, persistence, and updates follow different patterns. This skill guides Claude, Codex, and Claude Code toward one StoreBuilder approach.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "superpower-zustand" from https://skillstore.io/skills/cygnusfear-superpower-zustand.md and its manifest at https://skillstore.io/api/skills/cygnusfear-superpower-zustand/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.

Markdown detail GET /skills/cygnusfear-superpower-zustand.md Signed manifest GET /api/skills/cygnusfear-superpower-zustand/manifest Signed lockfile GET /api/skills/cygnusfear-superpower-zustand/lockfile

Test it

Using "superpower-zustand". Create a cart store with add, remove, and clear actions.

Expected outcome:

A typed Zustand store structure with cart state, factory actions, Immer updates, and an exported hook.

Using "superpower-zustand". Add persistence for user preferences only.

Expected outcome:

A persistence plan that stores safe preference fields while avoiding sensitive or temporary state.

Using "superpower-zustand". Review whether my store follows the required pattern.

Expected outcome:

State fields are separated from actions.
Actions are created through the factory.
Updates use Immer draft mutations.
Persistence is limited to appropriate fields.

Security Audit

Safe

v8 • 7/6/2026 Open versioned report

Static findings are false positives. The command execution hits are Markdown inline code, code fences, or TypeScript comments using backticks. The network and blocker hits are harmless documentation examples.

Files scanned

516

Lines analyzed

Review items

False positives ignored

Risk Factors

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

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.

Open versioned report

Copy report link

https://skillstore.io/skills/cygnusfear-superpower-zustand/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/cygnusfear-superpower-zustand/security.svg)](https://skillstore.io/skills/cygnusfear-superpower-zustand?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/cygnusfear-superpower-zustand?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cygnusfear-superpower-zustand/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/cygnusfear-superpower-zustand.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

Cygnusfear. (2026). superpower-zustand security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cygnusfear-superpower-zustand/audits/8

BibTeX citation

@techreport{cygnusfear-cygnusfear-superpower-zustand-2026,
  author = {Cygnusfear},
  title = {superpower-zustand security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/cygnusfear-superpower-zustand/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: "superpower-zustand security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
  - name: "Cygnusfear"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/cygnusfear-superpower-zustand/audits/8"
identifiers:
  - type: other
    value: "skillstore:cygnusfear-superpower-zustand:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Create Feature Stores

Build a new typed store with separate state, actions, and optional persistence.

Refactor Existing Stores

Convert inline Zustand actions into a consistent StoreBuilder factory structure.

Standardize Team Patterns

Document one repeatable store architecture for teams using Claude, Codex, or Claude Code.

Try These Prompts

Create a Basic Store

Create a Zustand store for a counter using the StoreBuilder pattern. Include state, actions, and the exported hook.

Add Persisted Preferences

Create a preferences store with theme and language fields. Use StoreBuilder persistence and persist only safe preference values.

Refactor an Existing Store

Refactor my existing Zustand store to use StoreBuilder. Separate state from actions and keep the public hook API stable.

Design an Async Domain Store

Design a StoreBuilder-based store for asynchronous todo loading. Include loading, error, mutation actions, and non-reactive access guidance.

Best Practices

Copy the StoreBuilder utility into a shared project location before creating stores.
Keep persisted fields narrow and avoid storing sensitive data.
Review generated stores with TypeScript checks and application tests.

Avoid

Mixing action methods into the initial state object.
Persisting entire stores when only preferences or identifiers need storage.
Using non-reactive state access inside React components when a hook selector is clearer.