email-design · fcakyon — Claude Code skill: what it does, how to install
email-design — a skill for Claude Code and Codex that handles transactional email layout. Styles account confirmations, password resets and billing receipts to match your application branding.
Apache-2.0 ★ 1,216 updated 2026-11-09
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install reusable-app-components@claude-settingsWhat email-design does
The skill defines guidelines for transactional messages such as email verification codes, password resets, payment receipts and product notices. It keeps the existing delivery pipeline and authentication logic intact instead of swapping out email providers for a visual redesign.
Layouts rely on fluid single-column presentation tables up to 560 px with inline CSS, explicit text colors and a matching plain-text part. It requires the light only color-scheme meta tag and the :root light dark declaration so that Gmail apps and Apple Mail do not invert dark mode into unreadable dark-on-dark blocks. Core content must avoid Flexbox, JavaScript, SVG and CSS background images.
Transparent PNG icons break when email clients shift backgrounds, so logos need their own solid backdrop. Browser previews cannot prove client rendering, meaning final templates must be inspected through test deliveries in the Gmail app and Apple Mail.
What it helps with
- build resilient transactional email templates that render across mail apps
- prevent dark mode color inversions from breaking contrast in Gmail
- format verification codes as selectable text with visible expiration times
- generate matching plain-text versions for all notification flows
Example prompts for the agent
- Design a verification email template matching our web app styles
- Review the password reset email markup for Apple Mail dark mode compatibility
- Create a transactional billing receipt template with inline CSS
How to install email-design
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install reusable-app-components@claude-settingsThis installs the whole reusable-app-components plugin with all its skills
2Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill email-design -a claude-code3Manually: put the files in place
~/.claude/skills/email-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/email-design/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill email-design -a codex2Manually: put the files in place
.agents/skills/email-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill email-design -a cursor2Manually: put the files in place
.cursor/skills/email-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install fcakyon/claude-codex-settings plugins/reusable-app-components/skills/email-design2Manually: put the files in place
.github/skills/email-design/SKILL.md1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill email-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/fcakyon/claude-codex-settings --path plugins/reusable-app-components/skills/email-designManually: put the files in place
.devin/skills/email-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about email-design
How to install email-design in Claude Code?
Run /plugin marketplace add fcakyon/claude-codex-settings in Claude Code, then run /plugin install reusable-app-components@claude-settings.
What does email-design do?
It guides the agent through constructing accessible, inline-styled transactional email templates that respect recipient mail client quirks and brand tokens.
Does this skill handle email marketing setups?
No, it targets transactional notifications and template integration inside existing application backends rather than marketing delivery services.
Source text
SKILL.md · Apache-2.0
--- name: email-design description: This skill should be used when user asks to "design app emails", "theme transactional emails", "fix verification emails", "build email templates", or "review password reset emails". Match an app’s brand and reuse its delivery pipeline across account, billing and notification emails. --- # App email design Make the email help someone finish the action they started in the app. Preserve the app’s transport, authentication and consent rules. Use this skill for transactional email design and integration, rather than email service setup or campaign sending. ## Inspect before changing Trace each requested event from the app action to its template and sending client. Check locales, HTML and text parts, provider-managed templates, sender, reply address, expiry and destination handling. Keep tokens, addresses and captured messages private. Find the shared layout before adding another renderer. Do not replace a working delivery service to change its design. Read the app’s visible theme and copy. Choose brand name, approved logo, page and surface backgrounds, body and muted text, primary action and its text color, font stack, corner radius and support address. Put these in one theme or layout, with message wording separate. Keep per-message content limited to subject, preview, heading, body, code or primary action, and necessary context. Use the app’s locale and runtime formatting for amounts and dates. ## Design around the action - Verification: show the code as selectable text, say where to enter it, and state the real expiry. Keep the code out of the subject and hidden preview. Do not make a link that only opens an unrelated homepage. - Password reset: continue the app’s actual recovery flow. Do not invent links, token lifetimes or automatic sign-in. Say what to do if the recipient did not request it. - Billing: show the amount, currency, period, renewal or cancellation date when relevant. Link to the exact plan or receipt. Do not shorten away billing terms or add upgrade pressure to a receipt. - Notifications: name the event and link to the affected item. Include preferences where supported. Keep marketing consent separate from required account messages. Use one main action. A code-entry email needs a readable code, rather than a competing button. Write direct headings such as “Verify your email” and “Reset your password”. Cut greetings, registration ceremony, congratulations and technical pipeline details when they do not help the next step. Remove accent rules, colored top edges and similar lines added only as decoration. Keep useful card surfaces, rounded corners, code highlights, brand color and spacing. Make the requested cleanup without flattening the surrounding design. ## Build for email readers Adapt [the layout asset](assets/email.html) to the app’s existing template engine. Its placeholder names describe content slots, not a required runtime. When the backend already wraps messages in its own document, as PocketBase does for auth emails, send only the asset's head tags and body content, and reset the wrapper's body padding and background. Replace its example theme with the app’s tokens. Keep action or code sections only when needed. Use the server’s escaping template engine for all dynamic text and validate action destinations where they are created. Never accept raw HTML from form fields or interpolate account data into markup. Use a fluid single column up to 560 px, presentation tables and inline CSS for essential layout. Include explicit foreground and background colors. Keep the light theme inline and put dark colors only in the asset's `prefers-color-scheme: dark` block. For a dark-only app, put its dark tokens inline and drop that block. In both cases keep the asset's `light only` color-scheme meta, because Gmail apps ignore `prefers-color-scheme`, recolor any email without it in dark mode and even turn dark emails light. Keep its `:root` `light dark` rule too: without it Apple Mail skips the dark block and recolors the email itself, which can leave dark text on a dark card. Keep the `x-apple-data-detectors` rule so Apple Mail does not underline codes, dates and addresses as links. Treat rounded corners as decoration. Use system font fallbacks, readable body text, large tap targets and underlined text links. Images need absolute HTTPS URLs and useful alt text. Clients that still recolor, including Gmail with non-Google accounts, change the surface but not images, so give logos and icons their own background instead of a white or black mark on a transparent PNG. Keep the message usable with remote images blocked, styles stripped or a screen reader. Use semantic headings and a logical reading order. Do not depend on JavaScript, web fonts, flexbox, SVG or background images for essential content. Send a matching plain-text part with the same action, code, expiry and required context. Keep secrets out of tracking URLs and do not add open tracking to account emails by default. Reuse verified sender and reply settings. Do not change DNS or delivery credentials as part of visual work. ## Verify the finished output Render the actual sending template with synthetic data in every changed locale. Inspect desktop and narrow screenshots, a long address or title, images blocked, and both HTML and text output. Check escaping with literal markup in user-supplied fields, action destinations, the issued code, and the real expiry against the owning backend. Exercise the real event against a local mail capture or an authorized test inbox, and check that inbox in dark mode in the Gmail app and Apple Mail, which recolor email in ways a browser preview cannot show. Preserve the selected app action through verification and recovery. A browser screenshot proves the template layout in that browser. Report actual inbox rendering and delivered mail separately, with the clients tested. Never claim Gmail, Apple Mail or Outlook compatibility from a browser preview alone. Do not send to real recipients, publish templates or change production pipelines without task authorization. Keep only requested previews and remove task captures containing real addresses or codes. References for rendering decisions: [HTML email structure](https://mailchimp.com/help/about-html-email) and [accessible email content](https://mailchimp.com/help/accessibility-in-email-marketing).
© Fatih C. Akyon · Apache-2.0 · fcakyon/claude-codex-settings
Similar skills
All skills for Design →email-design by other authors comes first.