store-best-practice

Original：🇨🇳 Chinese

Translated

4 scriptsChecked / no sensitive code detected

Generate best-practice store implementations using Zustand or similar state management libraries. Use this when you need to create scalable, type-safe stores, including proper slice patterns and provider setup.

2installs

Sourceforge-town/skills

Added on2026-02-16

NPX Install

npx skill4agent add forge-town/skills store-best-practice

SKILL.md Content (Chinese)

View Translation Comparison →

Store Best Practices

Provides best practice guidance and templates for creating and managing state management stores. Includes examples and best practices for slice patterns, store composition, type safety, provider setup, etc.

How It Works

Analyze application state requirements and determine the state slices to be managed
Strictly follow the code structure and patterns in [best-practice-examples/]
Create independent slice files for each state slice
Create a main store file to combine all slices
Implement a provider component to provide store context
Create barrel exports for clean imports
Use the generated store in the application

Scope of Capabilities

Responsibility Boundary: Only responsible for state storage, synchronization, and modification. Complex business logic (data validation, format conversion, business rule judgment) must be extracted into independent utility functions
Usage Boundary: Only used for "state sharing across components/modules". For component-private state, prioritize using
```
useState
```
/
```
useReducer
```
; overuse of stores is prohibited
Data Boundary: Do not store temporary/one-time data (such as temporary parameters for a single request), only store state that needs to be persisted or reused multiple times

Usage Instructions

This skill provides documentation and examples. Follow the steps in the reference guides:

Store Best Practice Guide - Detailed rules for store design and implementation
Best Practice Examples - Must strictly follow these Zustand store examples

Important: When implementing, you must strictly follow the code structure, naming conventions, and patterns in best-practice-examples. Any modifications may break type safety and maintainability.

Output

The skill will generate:

Independent slice files (one for each state slice)
Main store file (combines all slices)
Provider component (provides store context)
Barrel export file (index.ts)

Note: After invoking the skill, you must review the Checklist and ensure that the returned content fully matches all items in the checklist.

Troubleshooting

State management library not installed: Run
```
pnpm install zustand
```
in the project
Type errors: Check the state and action type definitions in the slice
Provider not set up correctly: Ensure the Provider is wrapped around the root component of the application
State not updating: Check if the actions in the slice correctly modify the state
Deviation from best practices: If you encounter issues, first confirm whether the code structure strictly follows the patterns in best-practice-examples