Instruction file imported from SDF-01/DevClientAssist (.cursor/rules/fullstack/notification-standard.mdc). Copyright stays with the author.

Notification Standard

Purpose

Standardize toasts, emails, alerts, and in app notifications.

When This Applies

• This rule applies when files matched by the glob are changed or generated.
• Use it when the task affects the behavior described by the purpose statement.

Required Workflow

1. Use existing notification primitives.
2. Make messages specific and actionable.
3. Handle delivery failures.
4. Avoid duplicate notifications for one event.

Standards

• Follow the existing project pattern before introducing a new one.
• Keep the implementation small, explicit, and easy to review.
• Prefer reusable project primitives, shared utilities, and documented conventions.
• Verify the change using the checks available in the project.

Do Not

• Do not spam users.
• Do not expose sensitive data in notifications.
• Do not send external messages without clear trigger.
• Do not use vague success or failure text.

Verification Checklist

• The existing project pattern was inspected before changes were made.
• The implementation is scoped to the user request.
• Unsafe files, secrets, and unrelated changes are excluded.
• Applicable lint, typecheck, test, build, or validation commands were run when available.
• Any skipped or failed verification is reported clearly.

Related Skills

• Use the matching .cursor/skills/ workflow when one exists for this rule.
• When no matching skill exists, follow this rule directly and keep changes minimal, safe, and verifiable.