rzyfront/vendix-notifications-system
skills/vendix-notifications-system/SKILL.md
Store notifications system: database notifications, SSE stream, Web Push/VAPID, subscriptions, and frontend NgRx integration. Trigger: When adding notification types, modifying SSE/Web Push delivery, notification preferences, or notification UI.
$ install --global
skillsauthnpx skillsauth add rzyfront/vendix vendix-notifications-systemInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 16, 2026, 5:08 AM26.3s1 file scanned
SKILL.md
- name:
- vendix-notifications-system
- description:
- >
- Store notifications system:
- database notifications, SSE stream, Web Push/VAPID, subscriptions, and frontend NgRx integration.
- Trigger:
- When adding notification types, modifying SSE/Web Push delivery, notification preferences, or notification UI.
- license:
- MIT
- author:
- rzyfront
- version:
- 1.0
- scope:
- [root]
Vendix Notifications System
Purpose
Use this skill for full-stack store notifications: persisted notification rows, SSE live stream, Web Push browser notifications, and notification preferences.
Current Architecture
NotificationsService.createAndBroadcast(...) is the hub:
- Creates a row in
notificationsusingGlobalPrismaService. - Broadcasts to connected store users through
NotificationsSseService. - Sends Web Push through
NotificationsPushService. - Catches/logs errors so notification failures do not break the business flow.
Delivery Channels
| Channel | Behavior |
| --- | --- |
| REST list/unread | Store-scoped persisted notifications |
| SSE | One Subject per store_id; every connected user for that store receives events |
| Web Push | Browser push via VAPID and push_subscriptions; filtered by notification_subscriptions.in_app |
| Email/WhatsApp preferences | Stored in notification_subscriptions, not used by generic notification delivery |
Backend Files
apps/backend/src/domains/store/notifications/notifications.controller.tsapps/backend/src/domains/store/notifications/notifications.service.tsapps/backend/src/domains/store/notifications/notifications-sse.service.tsapps/backend/src/domains/store/notifications/notifications-push.service.tsapps/backend/src/domains/store/notifications/notifications-events.listener.tsapps/backend/src/domains/store/notifications/dto/update-subscription.dto.tsapps/backend/src/domains/store/notifications/dto/push-subscription.dto.ts
Frontend Files
apps/frontend/src/app/core/services/notifications.service.tsapps/frontend/src/app/core/services/push-subscription.service.tsapps/frontend/src/app/core/store/notifications/*apps/frontend/src/app/shared/components/notifications-dropdown/notifications-dropdown.component.tsapps/frontend/src/app/private/modules/store/settings/general/components/notifications-settings-form/notifications-settings-form.component.tsapps/frontend/public/push-sw.js
API Endpoints
| Method | Endpoint | Purpose |
| --- | --- | --- |
| GET | /store/notifications | List notifications |
| GET | /store/notifications/unread-count | Unread count |
| PATCH | /store/notifications/:id/read | Mark one read; skips subscription gate |
| PATCH | /store/notifications/read-all | Mark all read; skips subscription gate |
| GET | /store/notifications/subscriptions | Read/init notification preferences |
| PATCH | /store/notifications/subscriptions | Update notification preferences |
| GET | /store/notifications/stream?token=JWT | SSE stream; token in query because EventSource has no custom headers |
| GET | /store/notifications/push/vapid-key | Public VAPID key |
| PATCH | /store/notifications/push/subscribe | Save browser push subscription |
| PATCH | /store/notifications/push/unsubscribe | Remove browser push subscription |
Prisma Reality
notificationshasstore_id,type,severity,title,body,data,is_read; nouser_id.notification_subscriptionshasstore_id,user_id,type,in_app,email,whatsapp.push_subscriptionsstores browser endpoints and keys perstore_id,user_id, and endpoint.notification_type_enumis the source of valid types. Listener-emitted types must exist in this enum.
Adding A Notification Type
- Add the type to
notification_type_enumthrough a safe Prisma migration. - Add or update event listener handling in
notifications-events.listener.ts. - Ensure
createAndBroadcast(...)receives a valid enum value. - Add default subscription/preferences if users should control the type.
- Update frontend icon/label/rendering where needed.
- Consider Web Push behavior;
in_apppreferences affect push delivery.
Known Current Mismatches To Watch
- Some listener-emitted booking/data request types may not exist in
notification_type_enum; those creates fail and are swallowed bycreateAndBroadcast(). update-subscription.dto.tsand default subscription initialization cover only a subset of enum values.- SSE ignores per-user preferences; Web Push enforces
notification_subscriptions.in_app. - There is a subscription effects SSE consumer for
subscription.updated; confirm backend emits that type before relying on it.
Zoneless Frontend Rule
Angular 20 frontend effects use native EventSource callbacks without NgZone.run(). Do not reintroduce Zone.js patterns; follow vendix-zoneless-signals.
Related Skills
vendix-zoneless-signals- EventSource/NgRx frontend behaviorvendix-multi-tenant-context- Store context and scoped operationsvendix-subscription-gate- Store write gating and@SkipSubscriptionGatevendix-prisma-migrations- Adding enum values safely
Related Skills
rzyfront/mobile-dev
development
VerifiedTrustedCommunity
Mobile app development rules for Vendix Expo/React Native project. Trigger: When editing, creating, or modifying any file under apps/mobile, or when developing mobile-specific features.
5SKILL.mdUpdated May 29, 2026
rzyfront/vendix-subscription-gate
development
VerifiedTrustedCommunity
Feature gating by store subscription state: global store write guard, AI feature gate, Redis feature resolution, quota consumption, frontend paywall interceptor, banner, and subscription UI states. Trigger: When adding feature gates, paywalls, subscription-based access control, protecting store write operations, AI feature gates, or rollout flags.
5SKILL.mdUpdated May 16, 2026
rzyfront/vendix-saas-billing
testing
VerifiedTrustedCommunity
SaaS subscription billing for Vendix stores: plan pricing, invoices, Wompi platform payments, manual payments, partner commissions, payouts, proration, and dunning. Trigger: When creating SaaS invoices, working with partner rev-share, margin/surcharge pricing, invoice sequence allocation, partner payout batches, subscription payments, manual payments, or dunning flows.
5SKILL.mdUpdated May 16, 2026
rzyfront/vendix-redis-quota
development
VerifiedTrustedCommunity
Periodic quota counters with Redis, UTC period keys, Lua-based idempotent AI quota consumption, request-id deduplication, and post-success consumption. Trigger: When building quota counters, enforcing monthly/daily feature caps, or reusing AI quota patterns for uploads, emails, exports, or rate-limited features.
5SKILL.mdUpdated May 16, 2026