real-time-updates

What problem does it solve?

Real-time updates help you avoid showing stale or misleading information by making browser freshness explicit for live dashboards, notifications, and progress views.

Core Features & Use Cases

• Freshness contract first: define acceptable staleness and user disruption rules before choosing a transport.
• Transport selection guidance: choose adaptive polling, Server-Sent Events (SSE), or bidirectional sockets based on directionality and recovery needs.
• Webhook-to-UI propagation patterns: route external changes through durable state updates and a browser reconciliation step.
• Optimistic update safety: apply speculative UI only when reversible, with rollback and server reconciliation.
• Reconnect and catch-up: implement reconnect that fetches missed state via versioning/cursors/timestamps and deduplicates updates.
• Stale-data indicators: show timestamps, connection/badge status, and non-disruptive “new data available” behavior.

Quick Start

Use the real-time-updates skill to design a browser freshness contract and pick the right mechanism (polling, SSE, or sockets) for your live dashboard’s user-visible update and recovery behavior.