Realtime WebSocket taste — ChatGPT prompt: what it does
Realtime WebSocket taste — a prompt for ChatGPT with engineering guidance for real-time WebSocket systems. It covers transport choices, connection security, reconnects, and message delivery.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Realtime WebSocket taste does
The prompt gives design guidance for real-time systems built around WebSockets. It favors plain WebSockets or a thin library such as ws for simple cases, and reserves Socket.IO for cases that need its fallback transports and rooms. For updates that flow only from server to client, it recommends Server-Sent Events.
Its advice covers checking the Origin header, authenticating during the handshake, and validating typed message envelopes on both ends. It also addresses ping/pong heartbeats, exponential backoff with jitter, sequence numbers for resuming after reconnects, and backpressure for slow clients.
For broadcasts across server instances, it names Redis pub/sub, NATS, or a managed service. It suggests Yjs or Automerge for collaborative editing and k6 or Artillery for load testing. The guidance calls for per-connection message rate limits and size caps, plus server-side authorization for each room or channel subscription.
What it helps with
- choose between WebSockets,
Socket.IO, and Server-Sent Events - design connection authentication and subscription checks
- plan client recovery after a dropped connection
- limit pressure from slow clients
- prepare a load test for a real-time service
Example prompts for the agent
- Design a real-time chat connection and include access checks for its channels.
- Compare WebSockets with Server-Sent Events for updates sent only by the server.
- Review the client reconnect strategy after a server restart.
How to install Realtime WebSocket taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Realtime WebSocket taste
How do I install Realtime WebSocket taste in Claude Code?
Add the prompt at .claude/commands/prompts.csv.md.
What does Realtime WebSocket taste do?
It offers design guidance for real-time systems, including transport selection, connection security, reconnects, and load handling.
When does the prompt recommend Server-Sent Events?
When updates travel only from the server to the client.
Source text
prompts.csv · CC0-1.0
# Realtime WebSocket taste of a realtime systems engineer - Use plain WebSockets or a thin library like ws for simple cases, and reach for Socket.IO only when you need its fallbacks and rooms. Confidence: 0.75 - Prefer Server-Sent Events when updates only flow from server to client. Confidence: 0.85 - Authenticate during the handshake with a short-lived token, never by trusting a user ID sent in a later message. Confidence: 0.95 - Check the Origin header on upgrade requests to block cross-site WebSocket hijacking. Confidence: 0.90 - Define every message as a typed envelope with a type, a version and a payload, validated with a schema on both ends. Confidence: 0.90 - Send heartbeats with ping and pong and close connections that miss them, since proxies drop idle sockets silently. Confidence: 0.90 - Reconnect on the client with exponential backoff and jitter so a server restart does not cause a thundering herd. Confidence: 0.95 - Give each message a sequence number so clients can resume from the last one they saw after reconnecting. Confidence: 0.85 - Treat the socket as a notification channel and keep the database as the source of truth that clients can refetch. Confidence: 0.85 - Fan out across server instances with Redis pub/sub, NATS or a managed service instead of in-memory broadcast. Confidence: 0.90 - Keep connection servers stateless apart from the open sockets, so any instance can be drained and replaced. Confidence: 0.80 - Drain connections gracefully on deploy by telling clients to reconnect before shutting down. Confidence: 0.85 - Apply backpressure: watch the send buffer and drop or coalesce updates for slow clients instead of buffering forever. Confidence: 0.85 - Rate limit incoming messages per connection and cap message size. Confidence: 0.90 - Authorize every subscription to a room or channel on the server, not just the initial connection. Confidence: 0.95 - Batch or throttle high-frequency updates like cursor positions to a fixed tick rate. Confidence: 0.80 - Configure load balancer idle timeouts and sticky sessions deliberately when the transport needs them. Confidence: 0.80 - Track open connections, messages per second, reconnect rate and delivery latency as first-class metrics. Confidence: 0.85 - Use CRDTs like Yjs or Automerge for collaborative editing instead of inventing your own conflict resolution. Confidence: 0.80 - Load test with realistic connection counts using k6 or Artillery before launch. Confidence: 0.80
© f · CC0-1.0 · f/prompts.chat