Nostr Client Patterns

Overview

Implement robust Nostr client architecture. This skill covers the patterns agents miss: relay pool connection management, subscription state machines that correctly handle EOSE/CLOSED transitions, event deduplication across relays, optimistic UI with OK message error recovery, and reconnection with gap-free event delivery.

When to Use

• The task is building or debugging a Nostr client’s relay, subscription, caching, publish, or reconnect architecture.
• The user needs client-side patterns for handling relay pools, EOSE/CLOSED states, deduplication, or optimistic UI.
• The problem is lifecycle management of events in a client, not protocol selection or relay-server code.
• The request involves missed events, duplicate events, relay churn, or local cache behavior.

Do NOT use when: