Add Email Notifications Automatically

The problem

Transactional emails are often hardcoded into logic, leading to duplicate code and security risks. Developers frequently waste time manually configuring SMTP settings, templates, and environment variables across different frameworks.

What it does

• Detects your project stack and architecture to implement a native email service.
• Creates reusable, template-based email flows for welcome messages, password resets, and order notifications.
• Sets up secure environment variable placeholders in .env.example to prevent credential leaks.
• Adds plain-text fallbacks and sanitizes user-provided template data for security.
• Integrates with existing providers or sets up a provider-neutral adapter for local development.

Frameworks & tools

Works with any stack including Node.js, Python, or PHP. Supports SMTP and major delivery providers.

Why this beats prompting it yourself

This skill enforces a strict separation between message creation and delivery, preventing architectural debt. It automatically handles security best practices like template sanitization and credential management that are easily missed in manual prompts.

Use cases

• Implement a "Forgot Password" flow with secure token placeholders.
• Create a reusable transactional email service for a new SaaS project.
• Add automated order confirmation and invoice emails to a checkout route.
• Migrate hardcoded HTML emails into a clean, template-driven system.

Known limitations

Will not perform real email delivery without explicit user approval and valid credentials. Requires an existing project structure to detect framework conventions.