zustand

Organize each slice with initialState.ts, action.ts, selectors.ts, and an optional reducer.ts under src/store slices directories. Aggregate slice states and actions in top-level initialState.ts and store.ts files, and export selectors through an xxxSelectors object.

Dispatch a temporary state update immediately with a generated temp ID, then call the backend service, and finally refresh the data for consistency. Delete operations should skip optimistic updates because recovery from destructive actions is complex.

Use the reducer pattern when managing object lists or maps, performing optimistic updates, or handling complex state transitions. Use a simple set call for toggling booleans, updating single values, or setting individual state fields.

Define a class that receives set, get, and api in its constructor, store them as private fields, and expose only public methods via Pick typing. Compose multiple class instances in the store using flattenActions instead of spreading them.

Internal actions contain core business logic like optimistic updates and service calls that require orchestration. Public actions handle parameter validation and flow control, so bypassing them risks inconsistent state and unvalidated inputs.