What problem does it solve? Building real-time collaborative features like shared counters, cursor positions, and synced Redux stores requires correct use of Velt's Live State Sync APIs, and mistakes with authentication, subscription cleanup, or data persistence lead to broken or leaky implementations. ## Core Features & Use Cases - API Selection Guidance: Rules for choosing between useLiveState, useSetLiveStateData/useLiveStateData, the LiveStateSyncElement observable API, and Redux middleware based on your use case. - Redux Store Sync: Patterns for createLiveStateMiddleware with action filtering (allowedActionTypes, disabledActionTypes) and dynamic liveStateDataId switching per document or room. - Server-Side Broadcast: REST API v1/v2 endpoints for pushing live state updates from your backend with merge support. - Use Case: Build a collaborative canvas where shape actions sync across all clients via Redux middleware while local UI actions stay unsynced, with connection status indicators and proper cleanup of ephemeral cursor data. ## Quick Start Ask the agent to build a React shared counter component using Velt Live State Sync with VeltProvider authProvider setup and a connection status indicator.