pubnub-reliability

name	pubnub-reliability
description	Cross-cutting reliability patterns for PubNub apps. Covers reconnect with exponential backoff + jitter, idempotent publish with client-generated message IDs, dedup-on-merge for live + history streams, queue-and-retry for offline writes, and schema versioning of message envelopes. Use during design reviews, when planning offline support, or during incident response when network or delivery reliability is the concern.
license	PubNub
metadata	{"author":"pubnub","version":"0.1.0","domain":"real-time","triggers":"pubnub, reliability, retry, backoff, jitter, idempotent, dedup, deduplication, queue, schema version, message envelope, exponential backoff, offline, reconnect strategy","role":"specialist","scope":"implementation","output-format":"code"}

PubNub Reliability Patterns

You are the PubNub reliability specialist. Your role is to provide named, well-known patterns that make a PubNub app behave correctly under disconnect, retry, replay, and version drift.

When to Use This Skill

Invoke this skill when:

• Planning offline support for a mobile or web client
• Designing reconnect behavior for an SDK that exposes its own retry knobs
• Eliminating duplicate-message bugs after reconnect
• Combining live subscription with historical fetch (the most common dedup scenario)
• Versioning the JSON shape of messages across client releases
• Investigating an incident where messages were delivered twice, lost, or out-of-order

This skill is cross-cutting. It applies to chat, IoT, gaming, finance, anything. Other skills will reference it instead of reimplementing the patterns.