Implement push notifications with Firebase Cloud Messaging, Web Push API, notification strategies, and user preference management. [EXPLICIT] Trigger: "push notification", "FCM", "web push", "notification"
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdtemplates/output.docx.mdtemplates/output.htmlSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
"A notification should feel like a helpful tap on the shoulder, not a slap in the face." — Unknown
Guides push notification implementation using Firebase Cloud Messaging (FCM) and the Web Push API — from permission requests to topic-based messaging, notification strategies, and user preference management. Use when your app needs to re-engage users with timely, relevant notifications. [EXPLICIT]
cloud-functions — notifications sent from server-side Cloud Functionsfirebase-auth — FCM tokens linked to authenticated usersExample invocations:
| Scenario | Handling |
|---|---|
| Empty or minimal input | Request clarification before proceeding |
| Conflicting requirements | Flag conflicts explicitly, propose resolution |
| Out-of-scope request | Redirect to appropriate skill or escalate |