Skip to content
Back to skills

State Management Design

ASecurity

Use for client state ownership across local, server, optimistic, persisted, form, auth, or cache boundaries.

  • 7 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 8, 2026
businessgobackend

Works with

  • cli

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add machenjie/rd-skills --skill state-management-design --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of State Management Design?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for State Management Design
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/machenjie-state-management-design/badge)](https://www.skillsdirectory.com/skills/machenjie-state-management-design)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: state-management-design
description: "Use for client state ownership across local, server, optimistic, persisted, form, auth, or cache boundaries."
---

# state-management-design

## Registry Trigger

**Use when**

- A state-ownership or lifetime decision is active.

**Do not use when**

- Skip work without a task-local state-management decision.

## Skill Role

Own state authority, identity, scope, transitions, persistence, cleanup, and evidence; exclude backend lifecycle, cache architecture, and permissions.

## High-Value Rules

- **Classify state.** Define authority, lifetime, and scope.
- **Bind ownership.** Define freshness keys from consumer and identity boundaries.
- **Close transitions.** Define async, optimistic, persistence, and cleanup behavior.

## Anti-Patterns

- Local success is not state-management contract proof.

## Stop Conditions

Stop on ambiguous authority, cross-identity state, unowned persistence, or unverified cleanup.

## Output Contract

- state-management decision with classification, authority and scope, identity and freshness, async and optimistic behavior, persistence policy, cleanup evidence, proof limits, and residual owners

## Targeted References

| Path | Type | Load when | Do not load when | Required by | Required output |
|---|---|---|---|---|---|
| [benchmarks and patterns](references/benchmarks-and-patterns.md) | benchmark-pattern | state ownership storage freshness invalidation or persistence choices remain unresolved | one authoritative owner determines storage lifecycle and reset behavior | task-agent | option-comparison, selected-approach |
| [checklist](references/checklist.md) | decision-checklist | change affects server UI form auth derived or persisted state | local state edit preserves ownership lifetime and synchronization | task-agent | checklist-result, residual-risk |
| [evidence patterns](references/evidence-patterns.md) | evidence-pattern | invalidation logout rollback or persistence claims need fresh proof | current stores hooks fixtures and tests prove each claim | task-agent | evidence-record, proof-limit, residual-risk |

Files in this skill

  • SKILL.md4 KB
  • examples/example-output.md3.8 KB
  • references/benchmarks-and-patterns.md3.8 KB
  • references/checklist.md2.1 KB
  • references/evidence-patterns.md3.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in business →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.