The body stays lean, cites RFC/spec sections by reference instead of re-explaining concepts Claude knows, and ties spec features to test assertions — every section earns its place rather than padding.

Provides multiple complete, executable Node.js/Jest code blocks (ws, eventsource+express, notification store, fan-out, reconnect, ordering) with real expect() assertions, plus executable Firebase patterns in the referenced file.

A clear numbered Steps 1–10 sequence is capped by a 'Test recipe checklist' (Step 10) that acts as a verification gate, and each pattern's assertions serve as the validation checkpoints for the testing workflow.

Firebase listener patterns are split into references/firebase-listener-tests.md and clearly signaled from Steps 4, 5, and 8; the verified reference file exists and contains the promised one-level-deep content.

Lists multiple concrete actions across four named transports plus 'fan-out to multiple sessions, offline-then-reconnect delivery, and ordering guarantees,' matching the 'lists multiple specific concrete actions' anchor; it exceeds the score-2 'some actions' bar.

Explicitly answers what (testing notifications across transports and behaviors) and when via 'Use when authoring tests for any notification that appears inside a connected web or mobile app UI,' matching the score-3 what-AND-when-with-explicit-triggers anchor.

Uses natural terms a user would say — 'in-app notifications,' 'WebSocket,' 'Server-Sent Events,' 'notification center,' 'read/unread state' — with good coverage rather than only jargon, matching the score-3 anchor.

States 'Distinct from email, SMS, push, and webhook channels' and scopes to in-app notifications over RFC 6455 / SSE / Firebase, giving a clear niche unlikely to trigger the wrong skill.