dyolink/.cursor/skills/notifications-inbox/SKILL.md

name, description

name	description
dyolink-notifications-inbox	Header notification bell/inbox (UserNotification fan-out + Socket.IO). Use when changing inbox cards, realtime gateway, or notification deep links — distinct from sidebar tab badges.

Notifications inbox (bell)

Permission-free feature (every dashboard user sees the bell). Cards are permission-filtered at fan-out time.

vs tab badges

	Inbox (UserNotification)	Sidebar badges (LabCaseActivity)
Entry	Header bell → dropdown + /notifications	Sidebar Cases/Tasks/Treatment/Orgs
Live	Socket.IO (/realtime)	REST + tab-badges-changed
Read	Per-card readAt only	Per-case / tab cursors

Do not clear tab badges when marking an inbox card read.

Backend

• Model: UserNotification + UserNotificationType in Prisma
• Fan-out: user-notification.service.ts
• Realtime: backend/src/realtime/ — RealtimeGateway (cookie JWT), RealtimeEmitter, rooms user:{userId}:org:{organizationId}
• REST: GET /notifications/inbox, GET /notifications/inbox/unread-count, POST /notifications/inbox/:id/read, POST /notifications/inbox/read-all

Emit sites (parallel to LabCaseActivity)

CASE_SENT, CLINIC_COMMENT, LAB_COMMENT (+ LAB_COMMENT_CLINIC), CASE_IMPORTANT, TASK_COMPLETED, TASK_ASSIGNED, CONNECTION_REQUEST, STAFF_INVITE — see plan / service call sites.

Frontend

• RealtimeProvider in dashboard layout
• NotificationBell + NotificationsPage + NotificationCard
• Deep links: /cases?caseId=, /tasks?taskId=, /treatment?labCaseId=, /organizations, /staff