Purpose

Web Push for CometChat chat. The web has no native VoIP-push equivalent for incoming-call ringing (see cometchat-react-calls/references/voip-and-web-push.md for that limit), but it does have Web Push for new-message notifications when the user's tab is backgrounded or closed. This skill wires the full path: client subscription → server webhook → push send → notification → click-through.

Not the same as the calls Web Push. Calls Web Push tries to ring the device through a closed tab (best-effort, browser-dependent). Chat Web Push notifies on new messages — fundamentally similar plumbing, different payload + UX. Many apps need both.

Read these other skills first:

cometchat-core — provider pattern, login order
cometchat-{react,nextjs,react-router,astro}-patterns — framework-specific Service Worker registration
cometchat-react-calls/references/voip-and-web-push.md — calls-specific Web Push (overlap with this; both can coexist)
cometchat-production — server-minted auth tokens (push payloads should NOT contain Auth Key)

Ground truth:

Web Push spec — https://datatracker.ietf.org/doc/html/rfc8030
VAPID — https://datatracker.ietf.org/doc/html/rfc8292
Push API — https://developer.mozilla.org/en-US/docs/Web/API/Push_API
CometChat dashboard PushNotifications (formerly Extensions → Enhanced Push Notifications)

cometchat-react-push

Purpose