AddThisFeature

Notification Center

An in-app inbox for everything that happened while users were away.

involved Engagement

What it adds

A persistent notification inbox with unread state, grouping, and preferences.

What your agent is told to do

4
  1. 1

    Model notifications as records, not ephemeral UI events, so they survive a reload.

  2. 2

    Add an unread count to the app's existing header or navigation.

  3. 3

    Group related notifications rather than emitting one row per event.

  4. 4

    Let users control which notifications they receive, and honour that preference.

Edge cases it handles

5
  • Never notify a user about their own action.
  • Deduplicate bursts — ten edits to one document is one notification, not ten.
  • A notification pointing at a deleted record must degrade gracefully, not 404.
  • Unread counts must stay correct across multiple open tabs.
  • Mark-all-as-read must be one request, not one per notification.

Definition of done

8
  • Notifications persist across sessions.
  • The unread count is accurate and updates across tabs.
  • Related notifications are grouped.
  • Users never receive notifications about their own actions.
  • Preferences are honoured.
  • Notifications for deleted records fail gracefully.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.