vndangkhoa/open-design
1
0
Fork 0
mirror of https://github.com/nexu-io/open-design.git synced 2026-05-31 19:04:39 +07:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
open-design/skills/email-marketing/SKILL.md
Tom Huang 6f6bf31dd2
Refactor project name from "Open Claude Design" to "Open Design" (#1) 
* Refactor project name from "Open Claude Design" to "Open Design"

- Updated project name in package.json, package-lock.json, and README files.
- Changed CLI commands and references from "ocd" to "od".
- Adjusted file structure references in documentation and code to reflect new naming conventions.
- Enhanced .gitignore to include new runtime data files.
- Updated metadata in LICENSE file to match new project name.

* Add contributing guidelines in English and Chinese

- Introduced CONTRIBUTING.md and CONTRIBUTING.zh-CN.md to provide clear instructions for contributors.
- Outlined contribution types, local setup instructions, and merging criteria for skills and design systems.
- Enhanced README files to reference the new contributing guidelines.
2026-04-28 16:03:35 +08:00

3.4 KiB
Raw Blame History

name description triggers od
email-marketing A brand product-launch email — masthead with wordmark, hero image block, headline lockup with skewed-italic accent, body copy, primary CTA, and a specifications grid. Pure HTML email layout (centered single column, table fallback). Use when the brief asks for an "email", "newsletter blast", "MJML", "product launch email", or "email template".
email
email template
newsletter
email blast
product launch email
mjml
邮件营销
邮件模板
mode platform scenario featured preview design_system example_prompt
prototype desktop marketing 3
type entry
html index.html
requires sections
true
color
typography
layout
components
Design a launch email for a sporty running shoe brand — masthead, hero, big headline lockup, specs grid, CTA.

Email Marketing Skill

Produce a single HTML email — centered, single column, no chrome around the email body. Treat it like a marketing artifact: one big idea, one CTA.

Workflow

  1. Read the active DESIGN.md (injected above). Email leans on the display font more than any other surface — pick the loudest type token in the DS for the headline lockup.
  2. Pick the brand + product from the brief. Generate a real wordmark, a real product name, and one real benefit sentence — no placeholders.
  3. Layout, in order, all centered inside a 600–680px column on a tinted page background (so the email body looks like an email, not the page):
    • Masthead — wordmark on the left + 3 short nav links (SHOP, JOURNAL, MEMBERS) on the right. Thin underline.
    • Hero block — a 16:9 product image placeholder. Use a DS-tinted gradient or a stylized SVG silhouette of the product (shoe, bottle, headphones, whatever the brief implies). Add a tiny brand stamp on the top-left and a colorway tag on the bottom-left.
    • Eyebrow — small caps, accent color, separated by · characters (e.g. "NEW · MAX-CUSHION TRAINER · EMBER FLARE").
    • Headline lockup — 2–3 line headline using the display font, all caps, extra-tight tracking. Apply a slight skew (transform: skew(-6deg)) on one accent word to give it a sporty parallelogram feel.
    • Body — 2–3 sentence paragraph, left-aligned, body font.
    • Primary CTA — solid pill or block button. One only.
    • Specs grid — 2×2 grid of (big number + unit + label) callouts using the display font for the numbers.
    • Footer — wordmark, address line, unsubscribe + view-in-browser links.
  4. Write a single HTML document:
    • <!doctype html> through </html>, CSS inline.
    • Center the column with margin: 0 auto. Set body { background: <tint> } so the email-on-page metaphor reads.
    • No external images — use inline SVG or DS-tinted gradient blocks for the product photo.
    • data-od-id on the masthead, hero, headline, CTA, specs.
  5. Self-check:
    • Email reads top to bottom in 8–10 seconds.
    • One CTA. Accent appears at most twice (eyebrow + CTA, or headline word).
    • Looks legible on a 480px window (column reflows, type drops one step).

Output contract

Emit between <artifact> tags:

<artifact identifier="email-slug" type="text/html" title="Email — Subject Line">
<!doctype html>
<html>...</html>
</artifact>

One sentence before the artifact, nothing after.