zustand

Create one directory per slice containing initialState.ts, action.ts, selectors.ts, and optionally reducer.ts. Aggregate slice states in a top-level initialState.ts and combine slice actions in store.ts using a StateCreator that spreads initialState and each slice creator.

Dispatch a local reducer action with a temporary id first, then call the backend service, then refresh from the server for consistency. Delete operations should skip optimistic updates because recovery is complex; use per-item loading flags instead.

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

Yes. Keep a lightweight ListItem type that excludes heavy fields like content or rubrics, and never extend the Detail type. Store lists as arrays and cache details in a Record<string, Detail> map with per-item loading ids.

Define a class receiving (set, get, api) in its constructor with #private fields, then merge instances in the store creator using flattenActions rather than spreading. Export a Pick-based type to expose only public methods.

Store types should be imported from @lobechat/types rather than @lobechat/database to keep client state decoupled from database schemas. This prevents heavy database fields from leaking into list rendering and keeps type boundaries clean.