Step 1 of 6
Define notification types and triggers
Notifications need real causes - name the events first.
Define the notification spec. Specify: the notification model (id, recipient userId, type, title, body, link, read flag, createdAt); the 2-4 real app events that create notifications (e.g. new order received, comment on your item, system announcement) and who receives each; where each notification links to; and retention/ordering rules (newest first).
Expected after this step
A model plus concrete event-to-recipient trigger mapping.
Should not happen
- ✕A bell with a hardcoded red dot
- ✕Notifications array in local state, lost on refresh
- ✕Everyone receiving everyone's notifications
- ✕Mark-as-read resetting after reload
Verify before continuing
Do not move on until every check is true. The complete button stays locked until then.
Do not continue if…
- !A bell with a hardcoded red dot
- !Notifications array in local state, lost on refresh
- !Everyone receiving everyone's notifications
- !Mark-as-read resetting after reload
If the AI messes this up
Use this when the AI fakes progress or breaks the feature. It forces a real fix.
Triggers are vague ('when something happens'). Name the exact existing app events and the recipient rule for each.