Transactional Notifications Engineer

What it does

Transactional Notifications Engineer is a Cursor agent playbook named notifications-engineer. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The notifications-engineer agent ships the mail and bells the product must send: magic links, invoices, payment failed, invite accepted. email-marketer owns nurture. This role owns deliverability basics, templates, and a preference center.

Welcome, magic link, invoice, in-app bell, unsubscribe. Builds transactional email and in-app notifications: templates, triggers, preference center. Not marketing drips.

Why it exists

A pile of agent files is not a team. notifications-engineer exists so one job, transactional notifications engineer, has a written brief, required skills, and a stop condition.

It ships in the Engineering Kit. Skills it must read: Transactional Email & In-App Notify; REST & API Route Design Patterns; Resilient Error Handling & Fault Tolerance. Commands that adopt this role: /notify: Transactional Email and In-App Notifications; /billing-fix: Stripe Dunning, Seats, and Portal Fixes; /auth-system: Authentication & Role-Based Access System.

When to use it

• Auth emails that look like spam
• Payment failed with no email
• Users begging to turn off one category of mail

When not to use it

• Do not ask notifications-engineer to do a different role's job. If you need a launch post, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Engineering Kit so .cursor/agents/notifications-engineer is on disk.
2. Run /notify: Transactional Email and In-App Notifications, or start a chat and tell Cursor to adopt the notifications-engineer role.
3. The agent should read: Transactional Email & In-App Notify; REST & API Route Design Patterns; Resilient Error Handling & Fault Tolerance.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are notifications-engineer. Auth emails that look like spam. Read transactional-notify before you edit."

Or let the pipeline invoke it: /notify: Transactional Email and In-App Notifications.

Capabilities you should actually see: Transactional templates with one job per message

Example output

• notifications-engineer should leave files or a written verdict, not a vibe check. Transactional templates with one job per message Trigger map from product events to sends
• Engineering agents should touch the slice they were given (schema, route, test, or review note) and nothing else.

Best practices

• Transactional templates with one job per message
• Trigger map from product events to sends
• In-app notification center + email twin
• Unsubscribe and preference storage
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using notifications-engineer as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Letting the writer approve its own PR.
• Invoking this agent and three unrelated ones in the same prompt.