hoangnguyen0403/nestjs-real-time
skills/nestjs/nestjs-real-time/SKILL.md
Implement WebSocket gateways with Socket.io and Server-Sent Events endpoints in NestJS. Use when building chat features, live feeds, or choosing between WebSocket and SSE for real-time communication.
$ install --global
skillsauthnpx skillsauth add hoangnguyen0403/agent-skills-standard nestjs-real-timeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 19, 2026, 3:36 AM62.7s3 files scanned
SKILL.md
- name:
- nestjs-real-time
- description:
- Implement WebSocket gateways with Socket.io and Server-Sent Events endpoints in NestJS. Use when building chat features, live feeds, or choosing between WebSocket and SSE for real-time communication.
Real-Time & WebSockets
Priority: P1 (OPERATIONAL)
Workflow: Add Real-Time Feature
- Choose protocol — WebSocket for bi-directional (chat, collab); SSE for uni-directional (feeds, notifications).
- Implement gateway or SSE — Create
@WebSocketGateway()or@Sse()controller. - Add auth — Validate JWT in
handleConnection()for WebSocket; use standard guards for SSE. - Scale — Add
@socket.io/redis-adapterfor multi-pod WebSocket; use HTTP/2 for SSE. - Test connections — Verify WebSocket handshake auth rejects invalid tokens; confirm SSE streams data.
SSE Endpoint Example
See implementation examples
WebSocket Gateway with Auth Example
See implementation examples
Protocol Selection
- WebSockets (Bi-directional): Use for Chat, Multiplayer Games, Collaborative Editing.
- High Complexity: Requires custom scaling (Redis Adapter) and sticky sessions (sometimes).
- Server-Sent Events (SSE) (Uni-directional): Use for Notifications, Live Feeds, Tickers, CI Log streaming.
- Low Complexity: Standard HTTP. Works with standard Load Balancers. Easy to secure.
- NestJS: Use
@Sse('route')returningObservable<MessageEvent>. - Long Polling: Use only as fallback or for extremely low-frequency updates (e.g., job status check every 10m).
- Impact: High header overhead. Blocks threads if not handled carefully.
WebSockets Implementation
- Socket.io: Default choice. Features "Rooms", "Namespaces", and automatic reconnection. Heavy protocol.
- Fastify/WS: Use
wsadapter if performance critical (e.g., high-frequency trading updates) and you don't need "Rooms" logic.
Scaling (Critical)
- WebSockets: In K8s, client connects to Pod . If Pod B emits event, client won't receive it.
- Solution: Redis Adapter (
@socket.io/redis-adapter). Every pod publishes to Redis; Redis distributes to all other pods. - SSE: Stateless. No special adapter needed, but aware of Connection Limits (6 concurrent connections per domain in HTTP/1.1; virtually unlimited in HTTP/2).
- Rule: Must use HTTP/2 for SSE at scale.
Security
- Handshake Auth: Standard HTTP Guards don't trigger on Ws connection efficiently.
- Pattern: Validate JWT during
handleConnection()lifecycle method. Disconnect immediately if invalid. - Rate Limiting: Sockets expensive. Apply strict throttling on "Message" events to prevent flooding.
Architecture
- Gateway != Service:
WebSocketGatewayshould only handle client comms (Join Room, Ack message). - Rule: Delegate business logic to Service or Command Bus.
- Events: Use
AsyncApiorSocketApidecorators (from community packages) to document WS events similarly to OpenAPI.
Anti-Patterns
- No HTTP guards for WebSocket auth: Validate JWT in
handleConnection(); HTTP guards don't trigger on WS. - No WebSocket at scale without Redis adapter: Without
@socket.io/redis-adapter, cross-pod events lost. - No SSE over HTTP/1.1 at scale: Use HTTP/2 to avoid 6-connection-per-domain browser limit.
Related Skills
hoangnguyen0403/common-operator-profile
testing
VerifiedTrustedCommunity
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
524SKILL.mdUpdated Jul 12, 2026
hoangnguyen0403/database-transactions
documentation
VerifiedTrustedCommunity
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-schema-design
development
VerifiedTrustedCommunity
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-query-performance
data-ai
VerifiedTrustedCommunity
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.
524SKILL.mdUpdated Jun 19, 2026