[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMY1GXZSANXAFMRJEPPXTW":3,"skill-same:01M7EMY1GXZSANXAFMRJEPPXTW":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMY1GXZSANXAFMRJEPPXTW","email-designer",null,"Design effective emails with inbox-friendly layouts, accessible HTML, dark mode, and testing checklists.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-email-designer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: email-designer\ndescription: Design effective emails with inbox-friendly layouts, accessible HTML, dark mode, and testing checklists.\ncategory: creative-design\n---\n\n## Overview\n\nEmail design is web design from 1999 that somehow still runs the world:\ninconsistent clients, no\nflexbox in Outlook, images blocked by default, and dark mode inversions. Yet\nemail drives more\nrevenue per effort than almost any channel. This skill covers designing emails\nthat render\neverywhere, get opened, and convert — from layout constraints to testing.\n\n## When to use\n\n- Designing marketing emails, newsletters, or transactional emails\n\n- Building email templates or design systems\n\n- Improving open rates, click rates, or conversions\n\n- Troubleshooting rendering issues across email clients\n\n- Planning dark mode support for emails\n\n## Core concepts\n\n- - - **The inbox is the first design.** Subject line, preheader, and sender\n  name determine opens\n  before the email is ever seen. Design the email backwards from the inbox:\nwould you open this?\n- - - **Single column, 600px.** The email standard: max-width 600px, single\n  column, generous spacing.\n  Multi-column layouts break on mobile (60%+ of opens) and in Outlook.\n- - - **Design for images-off.** Many clients block images by default. The email\n  must communicate with\n  text alone: real HTML text (not image text), alt text on every image,\nbackground colors as\n  fallbacks.\n- - - **Hierarchy for scanners.** Headline, hero visual, 2-3 content blocks max,\n  one primary CTA.\n  Email readers scan in seconds — long newsletters need ruthless editing or\nclear section anchors.\n- - - **The CTA rules.** One primary action per email, button-style (bulletproof\n  buttons: HTML text +\n  background color, not images), minimum 44px tall, repeated after long content.\nEvery link should\n  be obviously tappable.\n- - - **Dark mode is mandatory.** Clients auto-invert or apply dark themes.\n  Design with transparent\n  PNGs, test both modes, use meta tags where supported — and never rely on\n\"it'll be fine.\"\n\n## Practical workflow\n\n1. 1. 1. **Define the email's job.** One goal per email (click, purchase, reply,\n   read). Know the\n   audience segment and what they already know — relevance beats design polish.\n2. 2. 2. **Write inbox-first.** Subject line (under 50 characters, specific over\n   clever), preheader\n   (extends the subject, not repeats it), sender name (recognizable human or\nbrand).\n3. 3. 3. **Design the layout.** 600px single column: header (logo small, not\n   dominant), headline, hero,\n   body blocks, CTA, footer (unsubscribe prominent — hiding it creates spam\ncomplaints, which are\n   worse). Plain-text version included.\n4. 4. 4. **Build bulletproof HTML.** Table-based layout, inline CSS, web-safe\n   font stacks with\n   fallbacks, alt text everywhere, background colors behind images. Test in the\nbig three problem\n   clients: Outlook (Word engine), Gmail (strips \u003Cstyle> in some contexts),\nApple Mail.\n5. 5. 5. **Handle dark mode.** Test auto-inversions, use transparent images,\n   consider\n   dark-mode-specific meta styles. Check logos: a dark logo on a transparent\nbackground vanishes in\n   dark mode — use a white stroke version or contained logo block.\n6. 6. 6. **Check accessibility.** Semantic headings, meaningful alt text, 4.5:1\n   text contrast, logical\n   reading order, no text in images for critical content, sufficient tap\ntargets.\n7. 7. 7. **Test before sending.** Litmus\u002FEmail on Acid or manual: top clients\n   (Apple Mail, Gmail,\n   Outlook), mobile + desktop, images on\u002Foff, dark\u002Flight mode. Send a live test\nto yourself; click\n   every link. Check spam score basics (balanced image\u002Ftext ratio, no spam\ntrigger words in\n   subject).\n\n## Common pitfalls\n\n- - - **Image-only emails.** One big image with all the text baked in: blocked\n  by default in many\n  clients, unreadable, inaccessible, unclickable. Never.\n- - - **Tiny text.** Below 14px body text on mobile is unreadable. 16px body\n  minimum, generous line\n  height.\n- - - **Hidden unsubscribe.** Making it hard to leave generates spam complaints,\n  which tank\n  deliverability for everyone. One-click, visible unsubscribe.\n- - - **No plain-text version.** Multipart emails need a text fallback for\n  accessibility tools and\n  strict clients. Auto-generated is better than none; hand-tuned is best.\n- - - **Broken in Outlook.** Outlook's Word rendering engine ignores modern CSS.\n  If you didn't test\n  Outlook, you didn't test email.\n- - - **Subject-line clickbait.** \"You won't believe...\" gets opens and\n  unsubscribes. Specific, honest\n  subjects build the long-term list health that actually drives revenue.\n","## Overview\n\nEmail design is web design from 1999 that somehow still runs the world:\ninconsistent clients, no\nflexbox in Outlook, images blocked by default, and dark mode inversions. Yet\nemail drives more\nrevenue per effort than almost any channel. This skill covers designing emails\nthat render\neverywhere, get opened, and convert — from layout constraints to testing.\n\n## When to use\n\n- Designing marketing emails, newsletters, or transactional emails\n\n- Building email templates or design systems\n\n- Improving open rates, click rates, or conversions\n\n- Troubleshooting rendering issues across email clients\n\n- Planning dark mode support for emails\n\n## Core concepts\n\n- - - **The inbox is the first design.** Subject line, preheader, and sender\n  name determine opens\n  before the email is ever seen. Design the email backwards from the inbox:\nwould you open this?\n- - - **Single column, 600px.** The email standard: max-width 600px, single\n  column, generous spacing.\n  Multi-column layouts break on mobile (60%+ of opens) and in Outlook.\n- - - **Design for images-off.** Many clients block images by default. The email\n  must communicate with\n  text alone: real HTML text (not image text), alt text on every image,\nbackground colors as\n  fallbacks.\n- - - **Hierarchy for scanners.** Headline, hero visual, 2-3 content blocks max,\n  one primary CTA.\n  Email readers scan in seconds — long newsletters need ruthless editing or\nclear section anchors.\n- - - **The CTA rules.** One primary action per email, button-style (bulletproof\n  buttons: HTML text +\n  background color, not images), minimum 44px tall, repeated after long content.\nEvery link should\n  be obviously tappable.\n- - - **Dark mode is mandatory.** Clients auto-invert or apply dark themes.\n  Design with transparent\n  PNGs, test both modes, use meta tags where supported — and never rely on\n\"it'll be fine.\"\n\n## Practical workflow\n\n1. 1. 1. **Define the email's job.** One goal per email (click, purchase, reply,\n   read). Know the\n   audience segment and what they already know — relevance beats design polish.\n2. 2. 2. **Write inbox-first.** Subject line (under 50 characters, specific over\n   clever), preheader\n   (extends the subject, not repeats it), sender name (recognizable human or\nbrand).\n3. 3. 3. **Design the layout.** 600px single column: header (logo small, not\n   dominant), headline, hero,\n   body blocks, CTA, footer (unsubscribe prominent — hiding it creates spam\ncomplaints, which are\n   worse). Plain-text version included.\n4. 4. 4. **Build bulletproof HTML.** Table-based layout, inline CSS, web-safe\n   font stacks with\n   fallbacks, alt text everywhere, background colors behind images. Test in the\nbig three problem\n   clients: Outlook (Word engine), Gmail (strips \u003Cstyle> in some contexts),\nApple Mail.\n5. 5. 5. **Handle dark mode.** Test auto-inversions, use transparent images,\n   consider\n   dark-mode-specific meta styles. Check logos: a dark logo on a transparent\nbackground vanishes in\n   dark mode — use a white stroke version or contained logo block.\n6. 6. 6. **Check accessibility.** Semantic headings, meaningful alt text, 4.5:1\n   text contrast, logical\n   reading order, no text in images for critical content, sufficient tap\ntargets.\n7. 7. 7. **Test before sending.** Litmus\u002FEmail on Acid or manual: top clients\n   (Apple Mail, Gmail,\n   Outlook), mobile + desktop, images on\u002Foff, dark\u002Flight mode. Send a live test\nto yourself; click\n   every link. Check spam score basics (balanced image\u002Ftext ratio, no spam\ntrigger words in\n   subject).\n\n## Common pitfalls\n\n- - - **Image-only emails.** One big image with all the text baked in: blocked\n  by default in many\n  clients, unreadable, inaccessible, unclickable. Never.\n- - - **Tiny text.** Below 14px body text on mobile is unreadable. 16px body\n  minimum, generous line\n  height.\n- - - **Hidden unsubscribe.** Making it hard to leave generates spam complaints,\n  which tank\n  deliverability for everyone. One-click, visible unsubscribe.\n- - - **No plain-text version.** Multipart emails need a text fallback for\n  accessibility tools and\n  strict clients. Auto-generated is better than none; hand-tuned is best.\n- - - **Broken in Outlook.** Outlook's Word rendering engine ignores modern CSS.\n  If you didn't test\n  Outlook, you didn't test email.\n- - - **Subject-line clickbait.** \"You won't believe...\" gets opens and\n  unsubscribes. Specific, honest\n  subjects build the long-term list health that actually drives revenue.\n",{"name":5,"category":24,"description":7},"creative-design","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-email-designer",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill email-designer",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill email-designer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill email-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-email-designer\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","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\u002FCSS, 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.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","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).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]