Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Real Time Features

  • 493 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

real-time-features is an agent skill that guides developers through designing WebSocket, SSE, or pub/sub systems for live dashboards, chat, notifications, and collaborative editing in multi-client products.

About

real-time-features is a backend architecture skill from aj-geddes/useful-ai-prompts that helps developers choose and design real-time update patterns for multi-client applications. The skill covers WebSocket bidirectional channels, Server-Sent Events for server-push streams, and pub/sub fan-out for notifications, live dashboards, chat, and collaborative editing. A coding agent applies it when you need connection lifecycle, scaling, and channel-selection guidance rather than generic API design. Developers reach for real-time-features when adding live data to SaaS dashboards, in-app messaging, or shared document editing and want structured prompts instead of ad-hoc stack decisions.

  • Transport selection guidance
  • Event schema design prompts
  • Scaling and fan-out patterns
  • Reconnection and idempotency checks
  • Latency and ordering tradeoffs

Real Time Features by the numbers

  • 493 all-time installs (skills.sh)
  • Ranked #839 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill real-time-features

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs493
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you design WebSocket or SSE for live updates?

Design WebSocket, SSE, or pub/sub updates for live dashboards, chat, notifications, and collaborative editing in multi-client products.

Who is it for?

Backend developers adding live dashboards, chat, notifications, or collaborative editing to multi-client SaaS or API products.

Skip if: Teams that only need periodic REST polling or batch ETL jobs with no sub-second client updates.

When should I use this skill?

A developer asks to add live updates, real-time sync, WebSockets, SSE, or pub/sub to a multi-user application.

What you get

Real-time architecture decisions, channel diagrams, connection lifecycle notes, and pub/sub fan-out patterns for multi-client features.

  • Channel architecture recommendation
  • Connection lifecycle design notes

Files

SKILL.mdMarkdownGitHub ↗

Real-Time Features

Table of Contents

Overview

Implement real-time bidirectional communication between clients and servers for instant data synchronization and live updates.

When to Use

  • Chat and messaging applications
  • Live dashboards and analytics
  • Collaborative editing (Google Docs-style)
  • Real-time notifications
  • Live sports scores or stock tickers
  • Multiplayer games
  • Live auctions or bidding systems
  • IoT device monitoring
  • Real-time location tracking

Quick Start

Minimal working example:

// server.ts
import WebSocket, { WebSocketServer } from "ws";
import { createServer } from "http";

interface Message {
  type: "join" | "message" | "leave" | "typing";
  userId: string;
  username: string;
  content?: string;
  timestamp: number;
}

interface Client {
  ws: WebSocket;
  userId: string;
  username: string;
  roomId: string;
}

class ChatServer {
  private wss: WebSocketServer;
  private clients: Map<string, Client> = new Map();
  private rooms: Map<string, Set<string>> = new Map();

  constructor(port: number) {
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
WebSocket Server (Node.js)WebSocket Server (Node.js)
WebSocket Client (React)WebSocket Client (React)
Server-Sent Events (SSE)Server-Sent Events (SSE)
Socket.IO (Production-Ready)Socket.IO (Production-Ready)

Best Practices

✅ DO

  • Implement reconnection logic with exponential backoff
  • Use heartbeat/ping-pong to detect dead connections
  • Validate and sanitize all messages
  • Implement authentication and authorization
  • Handle connection limits and rate limiting
  • Use compression for large payloads
  • Implement proper error handling
  • Monitor connection health
  • Use rooms/channels for targeted messaging
  • Implement graceful shutdown

❌ DON'T

  • Send sensitive data without encryption
  • Keep connections open indefinitely without cleanup
  • Broadcast to all users when targeted messaging suffices
  • Ignore connection state management
  • Send large payloads frequently
  • Skip message validation
  • Forget about mobile/unstable connections
  • Ignore scaling considerations

Related skills

How it compares

Pick real-time-features when you need transport and fan-out architecture guidance before writing socket handlers or event brokers.

FAQ

When should developers use WebSocket vs SSE?

real-time-features recommends WebSockets for bidirectional chat and collaborative editing where clients send and receive events, and SSE for server-push streams like live dashboards and one-way notifications with simpler HTTP infrastructure.

What products benefit from real-time-features?

real-time-features targets multi-client SaaS with live dashboards, in-app chat, push notifications, or collaborative document editing where stale polling would hurt user experience and sub-second updates matter.

Backend & APIsbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.