SKILL-041 Emails and notifications Locked skill

In-app notification center

Notifications are per-user rows with a read_at timestamp — unread is the absence of read_at, not a separate boolean you have to keep in sync.

01

What this skill helps you build

A bell with an unread count, a dropdown list of per-user notifications, read/unread state, and mark-all-read.

The production takeaway

Notifications are per-user rows with a read_at timestamp — unread is the absence of read_at, not a separate boolean you have to keep in sync.

02

Inside this skill

The full skill expands these implementation areas with decisions, edge cases, prompts, tests, and framework-specific code.

Emails and notifications
What this helps you build

An in app notification center : the little bell in your top bar that shows an unread count, opens a dropdown of recent notifications, lets the user mark them read one at a time or

🔒
Emails and notifications
When to use this

Reach for an in app notification center when your app generates events the user cares about while they are using it, and email is too slow or too noisy: Someone mentioned, assigned

🔒
Emails and notifications
The core idea

A notification is a per user row — one recipient, one row. Fan out happens at write time: when an event occurs, you insert one notification per recipient. That makes reads trivial

🔒
03

Unlock the full implementation

Paid access includes the complete skill body, implementation prompt, common mistakes, production checklist, and code examples where this skill includes them.