一键在 Manus 中运行任何 Skill

zustand-store

星标0

分支1

更新时间2026年2月14日 03:43

Guidelines for global state management with Zustand. Trigger: When creating global stores, shared UI state, or managing session data.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

LuisDavidTF

LuisDavidTF/Vindex

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Core Principles

Minimalism: Store only what needs to be global.
Immutability: Updates should be immutable (Zustand handles this well, but be careful with nested objects).
Selectors: Use selectors to prevent unnecessary re-renders.

CRITICAL RULES

1. Store Definition

ALWAYS define stores in src/presentation/store/.
Predefine actions inside the store to modify the state.

interface BearState {
  bears: number;
  increase: (by: number) => void;
}

const useBearStore = create<BearState>()((set) => ({
  bears: 0,
  increase: (by) => set((state) => ({ bears: state.bears + by })),
}));

2. Logic Separation

NEVER put complex business logic inside the store actions. Call a UseCase, then update the store with the result.
Store = UI State (loading, modal open, current user).
Domain = Business Logic.

3. Selectors

ALWAYS select only the state you need in a component.

// Good
const bears = useBearStore((state) => state.bears);

// Bad (causes re-render on any change)
const { bears } = useBearStore();

同仓库更多 Skills

同仓库

learning-loop

LuisDavidTF/Vindex

Protocol for QA, error verification, and skill evolution to prevent recurring bugs.

2026-02-140

clean-arch

LuisDavidTF/Vindex

Guidelines for Domain-Driven Design and Clean Architecture dependency rules. Trigger: When creating new UseCases, Repositories, or planning module structure.

2026-02-140

drizzle-orm

LuisDavidTF/Vindex

Guidelines for using Drizzle ORM with SQLite. Trigger: When writing SQL queries, migrations, or modifying schema definitions.

2026-02-140

expo-managed

LuisDavidTF/Vindex

Expo Managed Workflow guidelines. Trigger: When configuring app.json, installing native libraries, or dealing with permissions/plugins.

2026-02-140

fontstock-db

LuisDavidTF/Vindex

FontStock Database Schema and Seeding. Trigger: When defining tables, relations, or initial data.

2026-02-140

fontstock-logic

LuisDavidTF/Vindex

FontStock business logic for inventory (expiry, search indexing). Trigger: When calculating dates, validating product inputs, or implementing search filters.

2026-02-140

name	zustand-store
description	Guidelines for global state management with Zustand. Trigger: When creating global stores, shared UI state, or managing session data.
license	Apache-2.0
metadata	{"author":"fontstock-arch","version":"1.0","scope":["ui"],"auto_invoke":"Managing Global App State"}
allowed-tools	Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task

Core Principles

Minimalism: Store only what needs to be global.
Immutability: Updates should be immutable (Zustand handles this well, but be careful with nested objects).
Selectors: Use selectors to prevent unnecessary re-renders.

CRITICAL RULES

1. Store Definition

ALWAYS define stores in src/presentation/store/.
Predefine actions inside the store to modify the state.

interface BearState {
  bears: number;
  increase: (by: number) => void;
}

const useBearStore = create<BearState>()((set) => ({
  bears: 0,
  increase: (by) => set((state) => ({ bears: state.bears + by })),
}));

2. Logic Separation

NEVER put complex business logic inside the store actions. Call a UseCase, then update the store with the result.
Store = UI State (loading, modal open, current user).
Domain = Business Logic.

3. Selectors

ALWAYS select only the state you need in a component.

// Good
const bears = useBearStore((state) => state.bears);

// Bad (causes re-render on any change)
const { bears } = useBearStore();