Email & Lifecycle Marketing
Email is the highest-ROI channel in SaaS — when done right. This skill helps you design email sequences that drive activation, retention, and revenue with specific copy you can paste into your email tool.
If
ABOUT-ME.mdand/orMY-ICP.mdexist in the project root, read them before writing emails. The "from" voice should match ABOUT-ME.md Communication Style — emails should sound like the founder, not a marketing department. The content should speak to MY-ICP.md — their pain, their goals, their language.
Core Principles
- Every email must answer: "Why should I care about this right now?"
- Behavioral triggers > time-based drips. React to what users DO, not how long they've been around.
- One email, one goal, one CTA. Multiple CTAs = no CTA.
- Subject lines determine whether your email is read. Body copy determines whether it's acted on.
- Unsubscribes are better than spam complaints. Make it easy to leave.
Part 1: Professional Branded Email (Do This First)
Before you send a single marketing email, you need a professional email address. Sending from yourname@gmail.com kills credibility. You want hello@yourdomain.com — and you can set this up for free in under 30 minutes.
More from whawkinsiv/claude-code-superpowers
secure
Use this skill when the user needs to secure their SaaS app, implement authentication, protect user data, secure APIs, or check for vulnerabilities. Also use when the user says 'is my app secure,' 'security check,' 'I'm worried about hackers,' 'how do I protect user data,' or 'security before launch.' Covers OWASP Top 10, auth best practices, data protection, and security checklists for apps built with AI tools.
158monitor
Use this skill when the user needs to set up production monitoring, track app health, configure error alerts, or respond to incidents. Also use when the user says 'my app went down,' 'how do I know if something breaks,' 'set up alerts,' 'is my app healthy,' or 'I found out from a user that my site was down.' Covers error tracking, uptime monitoring, performance metrics, and incident response for SaaS applications.
39debug
Use this skill when features break, users report errors, deployments fail, or tests don't pass. Guides systematic debugging: reproducing bugs, gathering diagnostic info, reading error messages, and working with AI tools to fix issues efficiently.
32build
Use this skill when the user needs to build features with AI coding tools, choose between Claude Code, Lovable, Replit, or Cursor, write effective prompts for code generation, or iterate on AI-generated code. Covers tool selection, prompting strategies, and development workflows for non-technical founders.
29test
Use this skill when the user needs to test features before deployment, create test scenarios, find edge cases, or verify bug fixes. Covers manual testing workflows, cross-browser testing, edge case identification, and testing checklists for non-technical founders.
23optimize
Use this skill when the user's app feels slow, the codebase feels bloated, or after significant development work. Also use when the user says 'my app is slow,' 'clean up my code,' 'reduce bundle size,' 'my hosting bill is too high,' or 'everything feels sluggish.' Optimizes across four dimensions: Speed (page load, API response), Code (unused files, dead code), Database (orphaned data, schema hygiene), and Dependencies (package bloat, bundle size).
22