frontend-state-management

TanStack Query handles server state orchestration while Zustand manages client UI state, creating a cohesive pattern that keeps complex social app frontends responsive and synchronized across multi-account contexts.

Offline persistence is achieved by setting up TanStack Query with an idb-keyval persister and wrapping the application with PersistQueryClientProvider, enabling offline-first behavior that survives page reloads and unstable connectivity scenarios.

Multi-account cache isolation safely purges caches on user switch while preserving per-device identifiers, utilizing structured query keys and selective revalidation to keep data fresh without triggering unnecessary reloads.

Yes, this approach is specifically designed for social app frontends facing offline, multi-account contexts, applying cross-account isolation guarantees and IndexedDB persistence to ensure smooth operation when connectivity is unstable.

Unnecessary reloads are prevented by implementing robust cache invalidation with structured query keys and selective queries invalidation, ensuring only the required data is revalidated rather than refreshing the entire cache.

YAML frontmatter containing name and description is required, while scripts, references, and assets are optional additions for implementing the strict cache invalidation, persistence, and isolation mechanisms.