push-notifications

SKILL.md

Expert decision frameworks for notification choices. Claude knows UNUserNotificationCenter and APNs — this skill provides judgment calls for permission timing, delivery strategies, and architecture trade-offs.

The trap: Requesting permission on first launch. Users deny reflexively. Wait for a moment when notifications clearly add value.

| alert | Visible notification | {title, subtitle, body} | | badge | App icon badge | Number | | sound | Notification sound | "default" or filename | | content-available | Silent/background | 1 | | mutable-content | Service extension | 1 | | category | Action buttons | Category identifier | | thread-id | Notification grouping | Thread identifier |

Expert notification decisions for iOS/tvOS: when to request permission, silent vs visible notification trade-offs, rich notification strategies, and APNs architecture choices. Use when implementing push notifications, debugging delivery issues, or designing notification UX. Trigger keywords: push notification, UNUserNotificationCenter, APNs, device token, silent notification, content-available, mutable-content, notification extension, notification actions, badge Source: kaakati/rails-enterprise-dev.

View raw