/emailDrafts a professional email. Subject, body, sign-off, all matched to the situation.
Category: Communication
Before / After
Write an email about X.
/email To my CTO. Asking for a 2-week deadline extension on the migration because the staging environment broke twice this week.
What changes in Claude's response
You get a complete email: a subject line that says what's inside (not 'quick question'), a body with one clear ask, and a sign-off that fits the relationship. /email knows that 'professional' depends on context — a CTO email is different from a customer email is different from a vendor email.
Full deep dive locked
The complete analysis for /email — including when NOT to use it, the failure modes, and the codes it stacks with — is in the full cheat sheet along with 119 other tested prefixes.
Lifetime updates · 3 tiers
More Communication codes
/replyDrafts a reply that matches the original tone, length, and energy.
/dmCasual short-form for chat platforms. No subject line, no sign-off, no markdown.
/announceAnnouncement-style copy. Big, clear, scannable, with the news in the first line.
/apologyGenuine, non-corporate apology. Names what you did wrong, what changes, no 'we're sorry if anyone felt'.
/thanksSpecific, sincere thank-you. No 'I just wanted to say thanks for everything'.
Get new codes + workflows weekly
Join 30+ developers getting tested prompt codes, skill files, and Claude workflows. One email when there’s something worth sharing.