AGENT SKILL

email-designer

Design effective emails with inbox-friendly layouts, accessible HTML, dark mode, and testing checklists.

License 许可
MIT
所属仓库
TanNhatCMS/jarvis
最近更新
2026-11-07
Stars
★ 0
Forks
1

01 前言 Front Matter

name
email-designer
category
creative-design
description
Design effective emails with inbox-friendly layouts, accessible HTML, dark mode, and testing checklists.

03 SKILL.md 正文

Overview

Email design is web design from 1999 that somehow still runs the world: inconsistent clients, no flexbox in Outlook, images blocked by default, and dark mode inversions. Yet email drives more revenue per effort than almost any channel. This skill covers designing emails that render everywhere, get opened, and convert — from layout constraints to testing.

When to use

  • Designing marketing emails, newsletters, or transactional emails

  • Building email templates or design systems

  • Improving open rates, click rates, or conversions

  • Troubleshooting rendering issues across email clients

  • Planning dark mode support for emails

Core concepts

      • The inbox is the first design. Subject line, preheader, and sender name determine opens before the email is ever seen. Design the email backwards from the inbox: would you open this?
      • Single column, 600px. The email standard: max-width 600px, single column, generous spacing. Multi-column layouts break on mobile (60%+ of opens) and in Outlook.
      • Design for images-off. Many clients block images by default. The email must communicate with text alone: real HTML text (not image text), alt text on every image, background colors as fallbacks.
      • Hierarchy for scanners. Headline, hero visual, 2-3 content blocks max, one primary CTA. Email readers scan in seconds — long newsletters need ruthless editing or clear section anchors.
      • The CTA rules. One primary action per email, button-style (bulletproof buttons: HTML text + background color, not images), minimum 44px tall, repeated after long content. Every link should be obviously tappable.
      • Dark mode is mandatory. Clients auto-invert or apply dark themes. Design with transparent PNGs, test both modes, use meta tags where supported — and never rely on "it'll be fine."

Practical workflow

      1. Define the email's job. One goal per email (click, purchase, reply, read). Know the audience segment and what they already know — relevance beats design polish.
      1. Write inbox-first. Subject line (under 50 characters, specific over clever), preheader (extends the subject, not repeats it), sender name (recognizable human or brand).
      1. Design the layout. 600px single column: header (logo small, not dominant), headline, hero, body blocks, CTA, footer (unsubscribe prominent — hiding it creates spam complaints, which are worse). Plain-text version included.
      1. Build bulletproof HTML. Table-based layout, inline CSS, web-safe font stacks with fallbacks, alt text everywhere, background colors behind images. Test in the big three problem clients: Outlook (Word engine), Gmail (strips <style> in some contexts), Apple Mail.
      1. Handle dark mode. Test auto-inversions, use transparent images, consider dark-mode-specific meta styles. Check logos: a dark logo on a transparent background vanishes in dark mode — use a white stroke version or contained logo block.
      1. Check accessibility. Semantic headings, meaningful alt text, 4.5:1 text contrast, logical reading order, no text in images for critical content, sufficient tap targets.
      1. Test before sending. Litmus/Email on Acid or manual: top clients (Apple Mail, Gmail, Outlook), mobile + desktop, images on/off, dark/light mode. Send a live test to yourself; click every link. Check spam score basics (balanced image/text ratio, no spam trigger words in subject).

Common pitfalls

      • Image-only emails. One big image with all the text baked in: blocked by default in many clients, unreadable, inaccessible, unclickable. Never.
      • Tiny text. Below 14px body text on mobile is unreadable. 16px body minimum, generous line height.
      • Hidden unsubscribe. Making it hard to leave generates spam complaints, which tank deliverability for everyone. One-click, visible unsubscribe.
      • No plain-text version. Multipart emails need a text fallback for accessibility tools and strict clients. Auto-generated is better than none; hand-tuned is best.
      • Broken in Outlook. Outlook's Word rendering engine ignores modern CSS. If you didn't test Outlook, you didn't test email.
      • Subject-line clickbait. "You won't believe..." gets opens and unsubscribes. Specific, honest subjects build the long-term list health that actually drives revenue.

04 同仓库更多 Skills

TanNhatCMS
TanNhatCMS/jarvis

web-scrape

Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

design-taste-frontend

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
TanNhatCMS
TanNhatCMS/jarvis

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
TanNhatCMS
TanNhatCMS/jarvis

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
TanNhatCMS
TanNhatCMS/jarvis

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

★ 0