[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV4AMRM7NKVBCD7GH2X4FY":3,"skill-same:01M7EV4AMRM7NKVBCD7GH2X4FY":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EV4AMRM7NKVBCD7GH2X4FY","notification-center",null,"Build notification centers — aggregation, preferences, read states, and unifying multi-channel alerts in one place.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-notification-center\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: notification-center\ndescription: Build notification centers — aggregation, preferences, read states, and unifying multi-channel alerts in one place.\ncategory: enterprise-communication\n---\n\n## Overview\n\nA notification center (the in-app bell icon) gives users one place to catch up on everything: mentions, updates, alerts, and announcements — with preferences to control it all. This skill covers designing notification centers: event modeling, aggregation, preferences, read states, and unifying email\u002Fpush\u002Fin-app into a coherent system.\n\n\nThe in-product notification center — the bell icon with your updates, alerts, and activity feed — is the safety net for all other channels: everything important lands there whether or not push\u002Femail was enabled or opened. Done well, it is a command center users check habitually; done poorly, it is a junk drawer of unread badges. Design it as a product, not an afterthought.\n## When to use\n\n- Building an in-app notification center\n- Unifying notifications across channels\n- Designing notification preferences\n- Reducing notification overload\n- Implementing read\u002Funread states\n- Planning notification infrastructure\n\n- Building an activity feed or alerts inbox\n- Reducing reliance on email for product updates\n- Designing notification preferences UX\n- Designing notification preferences and settings UX\n- Migrating users from email to in-app notifications\n- Building notification analytics\n## Core concepts\n\n**Event model.** Every notification derives from an event: actor, action, object, timestamp (e.g., \"Priya commented on Q3 Plan\"). Store events durably; render notifications from them. Good event modeling makes aggregation, filtering, and preferences possible.\n\n**Aggregation.** Group related events: \"Priya and 4 others commented\" beats 5 separate notifications. Aggregate by object + action type within time windows. Smart aggregation is the difference between useful and noisy.\n\n**Preferences.** Granular controls: per-category toggles (mentions, assignments, updates, announcements), per-channel routing (in-app only? + email? + push?), and digest options. Defaults matter — most users never change them, so ship sane defaults (important → push, routine → in-app only).\n\n**Read states.** Unread counts (accurate — phantom badges destroy trust), mark-as-read on view, mark-all-read, and per-item dismissal. Sync read states across devices — reading on desktop should clear mobile badges.\n\n**Channel orchestration.** The notification center is the hub; email\u002Fpush are spokes. Rules: urgent → all channels immediately; important → in-app + push; routine → in-app only (+ digest email). Avoid triple-notifying (push + email + in-app for the same event) unless user-configured.\n\n**Retention and performance.** Notification history (30–90 days typical), pagination\u002Fvirtualization for heavy users, real-time updates (websockets\u002Fpolling), and badge count accuracy. Performance at scale requires careful indexing on (user, timestamp).\n\n\n**Taxonomy and priority.** Categorize notifications (mentions, assignments, system alerts, social activity, marketing) and assign priority tiers: critical (badge + push + email), important (badge + center), informational (center only). Every notification type gets an explicit tier — unprioritized centers become noise, and noise gets ignored including the critical items.\n\n**Read states and badges.** Badge counts must be trustworthy: increment accurately, clear on view (or on read — pick one and be consistent), never show phantom counts. Nothing destroys notification trust faster than a badge that lies. Provide mark-all-read and per-category clearing.\n\n**Preferences architecture.** Granular controls per category (in-app, push, email toggles) with smart defaults (critical on, marketing off). The preferences screen is a retention tool — users who customize stay longer than users who globally disable. Make it discoverable from the center itself.\n\n**Smart batching.** Group related notifications (\"3 comments on your post\" not 3 separate) with time windows (batch within 15 minutes) and priority overrides (urgent breaks batches).\nBatching respects attention; unbatched streams train users to disable everything.\nLet power users configure batching granularity — control increases tolerance.\n**Cross-device sync.** Read states, dismissals, and preferences sync across web, iOS, and Android in real time.\nNothing erodes trust like clearing notifications on phone and finding them unread on desktop.\nImplement sync before launch — retrofitting is painful.\n**Analytics.** Delivery rate → open\u002Fview rate → action rate → opt-out rate per notification type.\nTrack the full funnel; high delivery with low action means irrelevant content, not technical success.\nCohort by notification type to find your noise offenders.\n## Practical workflow\n\n1. **Model events.** Catalog every notification-worthy event: category, importance, default channels, aggregation key, expiry. This catalog drives everything else.\n2. **Design the UI.** Bell icon with accurate badge, dropdown\u002Fpanel with grouped items, full-page history, filters by category, mark-all-read, and a prominent link to preferences. Mobile and desktop parity.\n3. **Build preferences.** Category toggles, channel routing per category, digest settings, quiet hours. Make it discoverable — buried preferences might as well not exist.\n4. **Implement aggregation.** Grouping rules per event type, time windows, and \"view all\" expansion. Test with high-volume scenarios — aggregation must hold under load.\n5. **Orchestrate channels.** Central dispatch rules: which events go to which channels, dedup across channels, and user overrides. One decision point, not per-channel logic scattered around.\n6. **Measure.** Notification volume per user, open\u002Fclick rates by category, preference change rates, opt-out rates, and support tickets about notifications. Tune defaults from data.\n\n**Event catalog template:** event name → category → default importance → default channels → aggregation key → expiry → preference toggle label.\n\n\n**Center design spec:** list view with rich previews (actor, action, object, timestamp) → grouping (\"5 people liked your post\" not 5 rows) → filters by category → empty states that teach (\"You're all caught up\" + preference link) → deep links to relevant content → retention policy (auto-archive after 90 days). Mobile and desktop parity — users switch devices mid-day.\n\n**Migration from email:** identify email notification types → add to center first (dual-delivery) → measure center engagement → offer \"reduce email\" prompts to engaged center users → gradually default new users to center-first. Never cut email abruptly — migrate by demonstrated preference.\n\n**Preferences UX patterns:** global kill switch (prominent) → category toggles → channel toggles per category (push\u002Femail\u002Fin-app) → frequency options (immediate\u002Fdigest\u002Foff) → quiet hours.\nProgressive disclosure: simple view by default, advanced for power users.\nTest with 5 users — confusing preferences get abandoned, then everything gets disabled.\n**Launch checklist:** taxonomy finalized → priority tiers assigned → badge logic tested → preferences built → analytics instrumented → seed content for empty states → migration plan from existing notifications.\nSoft-launch to 10% and watch opt-out rates before full rollout.\n## Common pitfalls\n\n- **No aggregation.** 50 notifications for one active thread. Aggregate or drown users.\n- **Phantom badges.** Counts that don't clear. Badge accuracy is trust — get it right.\n- **Triple notification.** Same event via push, email, and in-app simultaneously. Orchestrate centrally.\n- **Buried preferences.** Users can't find controls, so they disable everything or churn. Preferences must be one click from the bell.\n- **Bad defaults.** Defaulting everything to push. Ship conservative defaults; let users opt into more.\n- **No read-state sync.** Clearing on desktop, badge persists on phone. Sync everywhere.\n- **Infinite retention.** Storing years of notifications. Set retention (30–90 days) and archive or expire.\n- **Badge inflation.** Badging marketing messages alongside critical alerts. Users learn the badge means nothing and stop checking.\n- **No grouping.** 50 individual rows for one event thread. Aggregate aggressively — respect the user's scanning time.\n- **Missing preferences.** No way to tune what appears. The #1 reason users abandon notification centers is lack of control.\n- **Notification debt.** Launching new types without retiring old ones. Annual audits: every type justifies its existence with engagement data.\n- **Ignoring time zones.** Batching by server time instead of user local time. \"Good morning\" digests at 3am are a special kind of failure.\n","## Overview\n\nA notification center (the in-app bell icon) gives users one place to catch up on everything: mentions, updates, alerts, and announcements — with preferences to control it all. This skill covers designing notification centers: event modeling, aggregation, preferences, read states, and unifying email\u002Fpush\u002Fin-app into a coherent system.\n\n\nThe in-product notification center — the bell icon with your updates, alerts, and activity feed — is the safety net for all other channels: everything important lands there whether or not push\u002Femail was enabled or opened. Done well, it is a command center users check habitually; done poorly, it is a junk drawer of unread badges. Design it as a product, not an afterthought.\n## When to use\n\n- Building an in-app notification center\n- Unifying notifications across channels\n- Designing notification preferences\n- Reducing notification overload\n- Implementing read\u002Funread states\n- Planning notification infrastructure\n\n- Building an activity feed or alerts inbox\n- Reducing reliance on email for product updates\n- Designing notification preferences UX\n- Designing notification preferences and settings UX\n- Migrating users from email to in-app notifications\n- Building notification analytics\n## Core concepts\n\n**Event model.** Every notification derives from an event: actor, action, object, timestamp (e.g., \"Priya commented on Q3 Plan\"). Store events durably; render notifications from them. Good event modeling makes aggregation, filtering, and preferences possible.\n\n**Aggregation.** Group related events: \"Priya and 4 others commented\" beats 5 separate notifications. Aggregate by object + action type within time windows. Smart aggregation is the difference between useful and noisy.\n\n**Preferences.** Granular controls: per-category toggles (mentions, assignments, updates, announcements), per-channel routing (in-app only? + email? + push?), and digest options. Defaults matter — most users never change them, so ship sane defaults (important → push, routine → in-app only).\n\n**Read states.** Unread counts (accurate — phantom badges destroy trust), mark-as-read on view, mark-all-read, and per-item dismissal. Sync read states across devices — reading on desktop should clear mobile badges.\n\n**Channel orchestration.** The notification center is the hub; email\u002Fpush are spokes. Rules: urgent → all channels immediately; important → in-app + push; routine → in-app only (+ digest email). Avoid triple-notifying (push + email + in-app for the same event) unless user-configured.\n\n**Retention and performance.** Notification history (30–90 days typical), pagination\u002Fvirtualization for heavy users, real-time updates (websockets\u002Fpolling), and badge count accuracy. Performance at scale requires careful indexing on (user, timestamp).\n\n\n**Taxonomy and priority.** Categorize notifications (mentions, assignments, system alerts, social activity, marketing) and assign priority tiers: critical (badge + push + email), important (badge + center), informational (center only). Every notification type gets an explicit tier — unprioritized centers become noise, and noise gets ignored including the critical items.\n\n**Read states and badges.** Badge counts must be trustworthy: increment accurately, clear on view (or on read — pick one and be consistent), never show phantom counts. Nothing destroys notification trust faster than a badge that lies. Provide mark-all-read and per-category clearing.\n\n**Preferences architecture.** Granular controls per category (in-app, push, email toggles) with smart defaults (critical on, marketing off). The preferences screen is a retention tool — users who customize stay longer than users who globally disable. Make it discoverable from the center itself.\n\n**Smart batching.** Group related notifications (\"3 comments on your post\" not 3 separate) with time windows (batch within 15 minutes) and priority overrides (urgent breaks batches).\nBatching respects attention; unbatched streams train users to disable everything.\nLet power users configure batching granularity — control increases tolerance.\n**Cross-device sync.** Read states, dismissals, and preferences sync across web, iOS, and Android in real time.\nNothing erodes trust like clearing notifications on phone and finding them unread on desktop.\nImplement sync before launch — retrofitting is painful.\n**Analytics.** Delivery rate → open\u002Fview rate → action rate → opt-out rate per notification type.\nTrack the full funnel; high delivery with low action means irrelevant content, not technical success.\nCohort by notification type to find your noise offenders.\n## Practical workflow\n\n1. **Model events.** Catalog every notification-worthy event: category, importance, default channels, aggregation key, expiry. This catalog drives everything else.\n2. **Design the UI.** Bell icon with accurate badge, dropdown\u002Fpanel with grouped items, full-page history, filters by category, mark-all-read, and a prominent link to preferences. Mobile and desktop parity.\n3. **Build preferences.** Category toggles, channel routing per category, digest settings, quiet hours. Make it discoverable — buried preferences might as well not exist.\n4. **Implement aggregation.** Grouping rules per event type, time windows, and \"view all\" expansion. Test with high-volume scenarios — aggregation must hold under load.\n5. **Orchestrate channels.** Central dispatch rules: which events go to which channels, dedup across channels, and user overrides. One decision point, not per-channel logic scattered around.\n6. **Measure.** Notification volume per user, open\u002Fclick rates by category, preference change rates, opt-out rates, and support tickets about notifications. Tune defaults from data.\n\n**Event catalog template:** event name → category → default importance → default channels → aggregation key → expiry → preference toggle label.\n\n\n**Center design spec:** list view with rich previews (actor, action, object, timestamp) → grouping (\"5 people liked your post\" not 5 rows) → filters by category → empty states that teach (\"You're all caught up\" + preference link) → deep links to relevant content → retention policy (auto-archive after 90 days). Mobile and desktop parity — users switch devices mid-day.\n\n**Migration from email:** identify email notification types → add to center first (dual-delivery) → measure center engagement → offer \"reduce email\" prompts to engaged center users → gradually default new users to center-first. Never cut email abruptly — migrate by demonstrated preference.\n\n**Preferences UX patterns:** global kill switch (prominent) → category toggles → channel toggles per category (push\u002Femail\u002Fin-app) → frequency options (immediate\u002Fdigest\u002Foff) → quiet hours.\nProgressive disclosure: simple view by default, advanced for power users.\nTest with 5 users — confusing preferences get abandoned, then everything gets disabled.\n**Launch checklist:** taxonomy finalized → priority tiers assigned → badge logic tested → preferences built → analytics instrumented → seed content for empty states → migration plan from existing notifications.\nSoft-launch to 10% and watch opt-out rates before full rollout.\n## Common pitfalls\n\n- **No aggregation.** 50 notifications for one active thread. Aggregate or drown users.\n- **Phantom badges.** Counts that don't clear. Badge accuracy is trust — get it right.\n- **Triple notification.** Same event via push, email, and in-app simultaneously. Orchestrate centrally.\n- **Buried preferences.** Users can't find controls, so they disable everything or churn. Preferences must be one click from the bell.\n- **Bad defaults.** Defaulting everything to push. Ship conservative defaults; let users opt into more.\n- **No read-state sync.** Clearing on desktop, badge persists on phone. Sync everywhere.\n- **Infinite retention.** Storing years of notifications. Set retention (30–90 days) and archive or expire.\n- **Badge inflation.** Badging marketing messages alongside critical alerts. Users learn the badge means nothing and stop checking.\n- **No grouping.** 50 individual rows for one event thread. Aggregate aggressively — respect the user's scanning time.\n- **Missing preferences.** No way to tune what appears. The #1 reason users abandon notification centers is lack of control.\n- **Notification debt.** Launching new types without retiring old ones. Annual audits: every type justifies its existence with engagement data.\n- **Ignoring time zones.** Batching by server time instead of user local time. \"Good morning\" digests at 3am are a special kind of failure.\n",{"name":5,"category":24,"description":7},"enterprise-communication","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-notification-center",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill notification-center",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill notification-center",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill notification-center","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-notification-center\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]