Ground truth: push is the CometChat Notifications product, not a UI Kit component — this skill is THIN and docs-first. Registration, payload shape and provider setup are FETCHED from the notifications docs via cometchat-angular-v5-core/references/docs-map.md; nothing about them is baked here. Live delivery cannot be auto-smoked — say so honestly rather than claiming verification.

Companion skills (read first)

cometchat-angular-v5-core — install, credentials, init→login→render. Assumed.

Use this skill when

Delivering notifications while the app is closed or backgrounded.

This skill is deliberately THIN — fetch the docs

Push spans a product (CometChat Notifications), a third-party provider (Firebase/FCM), a service worker, and browser permission rules. Every one of those changes independently, so a baked recipe goes stale fast.

Start here: {SDK_DOCS_BASE}/notifications/overview.md, then the web push integration page. Discover the current pages from the SDK index (cometchat-angular-v5-core/references/docs-map.md). Read before writing.

Angular's own docs cover push only inside {DOCS_BASE}/ui-kit/angular/campaigns.md — there is no dedicated Angular push page. That is a known docs gap; the product-level notifications docs are the source of truth.

What is true regardless of version

1. Push is a separate product. It must be enabled and configured for the app in the dashboard, with provider credentials added there. No client code substitutes for that step.

2. It is not the UI Kit. Registration is SDK-level (CometChatNotifications), not a component. There is nothing to render.

cometchat-angular-v5-push

Companion skills (read first)

Use this skill when

This skill is deliberately THIN — fetch the docs

What is true regardless of version