When the user wants to create or optimize an email sequence, drip campaign, or lifecycle email program — "nurture sequence," "onboarding emails," "welcome series," "re-engagement," "email automation," "email cadence," or any multi-email automated flow. For cold outreach, see cold-email. For in-app onboarding, see onboarding-cro.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
Establish:
One primary purpose and one main CTA per email — don't try to do everything.
Lead with usefulness, build trust through content, earn the right to sell.
Fewer, better emails win. Segment for relevance. Quality > frequency.
Every email moves them somewhere. Links should do something useful. Make next steps obvious.
Welcome 3-7 emails; lead nurture 5-10; onboarding 5-10; re-engagement 3-5 — scaled by sales cycle length, product complexity, and relationship stage.
Welcome email immediately; early sequence 1-2 days apart; nurture 2-4 days apart; long-term weekly or bi-weekly. B2B: avoid weekends. B2C: test weekends. Send at local time.
Clear > clever. Specific > vague. Benefit or curiosity-driven. 40-60 characters ideal. Test emoji (they're polarizing).
Patterns that work:
Extends the subject line, ~90-140 characters. Don't repeat the subject — complete the thought or add intrigue.
Length: 5-7 emails over 12-14 days. Goal: Activate, build trust, convert.
Length: 6-8 emails over 2-3 weeks. Goal: Build trust, demonstrate expertise, convert.
Length: 3-4 emails over 2 weeks. Trigger: 30-60 days of inactivity. Goal: Win back or clean list.
Length: 5-7 emails over 14 days. Goal: Activate, drive to aha moment, upgrade. Coordinate with in-app onboarding — email supports, doesn't duplicate.
Detailed templates: references/sequence-templates.md
Detailed email type reference: references/email-types.md
Short paragraphs (1-3 sentences), white space between sections, bullets for scanability, bold sparingly, mobile-first (most read on phone).
Conversational, not formal. First-person (I/we) and second-person (you). Active voice. Read it out loud — does it sound human?
50-125 words transactional; 150-300 educational; 300-500 story-driven.
Buttons for primary actions, links for secondary. One clear primary CTA per email. Button text: action + outcome.
Detailed copy, personalization, and testing guidelines: references/copy-guidelines.md
Sequence Name: [Name]
Trigger: [What starts the sequence]
Goal: [Primary conversion goal]
Length: [Number of emails]
Timing: [Delay between emails]
Exit Conditions: [When they leave the sequence]
Email [#]: [Name/Purpose]
Send: [Timing]
Subject: [Subject line]
Preview: [Preview text]
Body: [Full copy]
CTA: [Button text] → [Link destination]
Segment/Conditions: [If applicable]
What to measure and benchmarks.
For implementation, see the tools registry. Key email tools:
| Tool | Best For | MCP | Guide |
|---|---|---|---|
| Customer.io | Behavior-based automation | - | customer-io.md |
| Mailchimp | SMB email marketing | ✓ | mailchimp.md |
| Resend | Developer-friendly transactional | ✓ | resend.md |
| SendGrid | Transactional email at scale | - | sendgrid.md |
| Kit | Creator/newsletter focused | - | kit.md |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.
The English summary is being prepared. Showing the original description.
When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
The English summary is being prepared. Showing the original description.
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.
The English summary is being prepared. Showing the original description.
When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.
The English summary is being prepared. Showing the original description.
When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.
The English summary is being prepared. Showing the original description.
Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.
The English summary is being prepared. Showing the original description.