email-marketing
When the user wants to plan email marketing, EDM, newsletter strategy, or email deliverability. Also use when the user mentions "email marketing," "EDM," "newsletter," "SPF," "DKIM," "DMARC," "email deliverability," "email content strategy," "email campaigns," "newsletter strategy," "email automation," or "cold email." For signup UI, use newsletter-signup-generator.
What this skill does
# Channels: Email Marketing Guides email marketing strategy for AI/SaaS products. Email ROI ~$36 per dollar spent; open/click rates typically higher than social. Covers EDM vs Newsletter, five content types, deliverability (SPF/DKIM/DMARC), and SEO synergy via article delivery. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for audience and content strategy. See **content-marketing** for content types and formats across channels. Identify: 1. **Goal**: Retention, conversion, brand reach, or SEO synergy 2. **Content mix**: Onboarding, campaign, announcement, features, newsletter 3. **List size**: Bulk sender rules (5,000+/day) require Gmail/Yahoo compliance ## EDM vs Newsletter | Type | Purpose | Use | |------|---------|-----| | **EDM** | Direct marketing; conversion-focused | Promotions, campaigns, announcements; bulk sends | | **Newsletter** | Ongoing value; relationship | Industry insights, curated articles; regular cadence | **Combine both**: EDM for push; Newsletter for nurture. Cover different stages and goals. ## Five Content Types | Type | Use | |------|-----| | **Onboarding** | Welcome + first-use guidance; 5-7 day sequence; behavior-triggered; drive "Aha!" moment | | **Campaign** | Promotions, limited-time; conversion or participation | | **Announcement** | Product launch, major update; one-time important notice | | **Features update** | New features, improvements; help users adopt | | **Blog/Newsletter** | Curated articles, industry insights; sustained touch | ## User Best Practices | Practice | Guideline | |----------|-----------| | **Personalization** | Segment by behavior, source, stage; boosts open/click | | **Timing** | New users: dense; existing: controlled pace; behavior-triggered > calendar-only | | **Welcome series** | Send soon after signup; 5-7 emails over days; guide first key action | | **Unsubscribe** | One-click required (Gmail/Yahoo); honor within 48h; clear entry | | **Complaint rate** | Keep below 0.3%; list hygiene critical | ## Content Best Practices | Practice | Guideline | |----------|-----------| | **Subject** | One clear topic per email; avoid pure promo | | **Value first** | Useful info before promotion | | **CTA** | Single primary CTA; clear next step | | **Mobile** | 50%+ read on mobile; responsive layout, tappable links | ## Deliverability & Domain Config **Subdomain**: Use subdomain (e.g. mail.example.com) for marketing; keep transactional (support@, etc.) on main domain. Isolate risk. ### SPF, DKIM, DMARC | Protocol | Purpose | |----------|---------| | **SPF** | Authorizes mail servers for domain | | **DKIM** | Cryptographic signature; verifies sender | | **DMARC** | Policy for unauthenticated mail; start p=none, then quarantine, then reject over 60-90 days | **Order**: SPF first, then DKIM, then DMARC. Gmail/Yahoo require all three for bulk senders (5,000+/day) since Feb 2024. **Advanced**: TLS-RPT, MTA-STS, BIMI (brand logo). **Postmaster Tools**: Monitor deliverability, spam rate, auth status. ## Delivery Strategy: Articles + SEO Synergy | Article Type | Use | |--------------|-----| | **Retention** | Deep content for existing users; improve retention | | **ToFu** | Top of funnel; awareness (trends, concepts, problem framing) | | **MoFu** | Middle of funnel; consideration (comparisons, reviews, best practices) | **Dual value**: (1) Better email engagement (open, click, stickiness); (2) Drive traffic to article pages from non-search channel; signals to Google that users value content; supports SEO. **Measurement**: GA4 email source traffic to article pages; GSC rank/click changes. ## Planning Framework 1. **Content mix**: Allocate onboarding, campaign, announcement, features, newsletter 2. **Select articles**: Pick retention, ToFu, MoFu from blog; prioritize SEO target pages 3. **Cadence**: Stable frequency (weekly/biweekly/monthly); avoid over-sending 4. **Monitor**: Open rate, click rate; GA4 email contribution to article traffic; GSC ## Frequency | Guideline | Note | |-----------|------| | **Baseline** | 1 high-value email/week for most brands | | **Peak times** | Tue-Thu, 8-11am or 2-4pm (recipient timezone) | | **Segmentation** | New vs loyal need different cadence | | **Quality** | Relevant, behavior-triggered > calendar volume | **Data**: ~36% send 1-3/month; ~30% weekly; daily risks high unsubscribe. ## Output Format - **Content mix** (five types) - **EDM vs Newsletter** balance - **Deliverability** (subdomain, SPF/DKIM/DMARC) - **Article delivery** (Retention, ToFu, MoFu, SEO targets) - **Cadence** and frequency - **KPI** (open, click, GA4 email traffic, GSC) ## Related Skills - **content-marketing**: Content types, formats; email as channel in repurposing matrix - **newsletter-signup-generator**: Signup form design - **traffic-analysis**: Email source attribution, UTM - **analytics-tracking**: Email click tracking - **content-strategy**: Article selection for email delivery - **integrated-marketing**: Email as owned media channel
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.