What problem does it solve? It standardizes how Zustand stores are structured in the LobeHub codebase, preventing inconsistent action naming, scattered slice organization, and incorrect optimistic update patterns when editing src/store code. ## Core Features & Use Cases - Action Type Hierarchy: Enforces the three-layer pattern of public actions, internal_* actions, and internal_dispatch* methods with clear responsibilities. - Optimistic Update Patterns: Provides proven create/update/delete flows with temporary IDs, reducer dispatches, and SWR cache refresh, including the rule that deletes skip optimistic updates. - Class-Based Slice Migration: Guides migration from plain StateCreator objects to class-based actions composed with flattenActions, including multi-class slices and store-access typing. - Use Case: When adding a new chat slice, follow the references to structure initialState, selectors, reducers, and actions consistently with existing slices like message and topic. ## Quick Start Ask the AI to refactor a Zustand store slice in src/store to follow the LobeHub action hierarchy and class-based action pattern.