kb-notifications

What problem does it solve?

This Skill solves the problem of notifications turning into inconsistent, duplicated, and hard-to-maintain UX and delivery logic across a Next.js app.

Core Features & Use Cases

• Categories × channels model: defines a stable matrix (system/transactional/behavioral/marketing × in-app/push/email) to prevent drift and enforce compliance (e.g., marketing opt-in).
• Toast vs persist UX policy: establishes when to show ephemeral toasts, when to store notifications for history, and when to do both.
• Real-time transport decision tree: guides whether to use SSE, polling, or WebSockets based on update shape and latency needs.
• Backpressure, ordering, and dedup rules: ensures DB-generated timestamps, dedup keys to prevent spam, and queue-based delivery to keep request paths fast.
• Preference storage guidance: recommends a flat schema that stays indexable and migration-friendly, with an alternative only when hierarchy truly requires JSON.

Quick Start

Ask the AI to design a notification system for your Next.js app that includes categories, channel preferences, toast/persist rules, and an SSE-based real-time delivery plan.