debug-sse

Diagnose SSE real-time update failures across endpoints, listeners, and query invalidation mappings.

15|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/aalmada/BookStore --skill debug-sse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-sse
Source: https://github.com/aalmada/BookStore/tree/main/.claude/skills/debug-sse
Command: npx skills add https://github.com/aalmada/BookStore --skill debug-sse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and fix Server-Sent Events (SSE) issues that prevent real-time frontend updates after data mutations.

Core Features & Use Cases

  • Validate SSE endpoint responsiveness
  • Verify DomainEventNotifications implementation and proper interface usage
  • Confirm MartenCommitListener handles projections and sends notifications
  • Ensure QueryInvalidationService maps notifications to frontend query keys
  • End-to-end verification of mutation → event → UI refresh

Quick Start

  • Test the SSE stream: curl -N -H "Accept: text/event-stream" http://localhost:5000/api/events
  • Check that DomainEventNotifications are defined and implement IDomainEventNotification
  • Inspect MartenCommitListener and QueryInvalidationService wiring to ensure proper notifications and key mappings

Frequently Asked Questions about debug-sse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why are my frontend SSE updates not refreshing after a backend data mutation?

Server-Sent Events (SSE) real-time updates fail when the mutation-to-UI refresh flow is broken. You need to verify endpoint availability, domain event notifications, projection listeners, and frontend query invalidation mappings to restore synchronization.

How do I test if my SSE endpoint is available and responding correctly?

Test your SSE endpoint by running a curl command with the event-stream header against your API URL to verify the stream is available, responsive, and actively pushing server-sent events to the client.

How do I map backend domain event notifications to frontend query invalidation?

Configure the QueryInvalidationService to map incoming domain event notifications to specific frontend query keys, ensuring that when the server-sent events listener receives a mutation event, the corresponding UI queries are invalidated and refreshed.

Does this SSE debugging workflow work with Marten projection listeners?

Yes, this workflow verifies that the MartenCommitListener is properly wired to handle projections and dispatch domain event notifications through the SSE stream, ensuring backend changes trigger the correct frontend query invalidation.

What should I check when server-sent events stop triggering UI refreshes?

When server-sent events stop triggering UI refreshes, inspect the MartenCommitListener and QueryInvalidationService wiring to ensure proper notifications are sent and frontend query key mappings are correctly configured for the mutation events.