VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Marketing Kit

/ak:email

Email Campaign Builder

Creates newsletters, cold emails, launches, nurture flows, welcome and winback campaigns with subject lines, preview text, body, and CTA.

01

Parse type

02

Gather context

03

Load reference

04

Draft variants

Rule 01

Email work starts with audience, message, and CTA, not with a template.

Rule 02

Subject lines need multiple testable variants, not a single best guess.

Rule 03

Deliverability is part of the copy contract when campaigns leave the draft stage.

Rule 04

Flows and sequences require the reference workflow before drafting individual emails.

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Parse type Read newsletter, cold, followup, launch, nurture, welcome, winback, flow, or sequence from the first argument.
  2. 2 Gather context Ask for audience, message, offer, CTA, timing, and any deliverability constraints.
02

Work

Agent / skill execution

  1. 3 Load reference For flow or sequence, load the matching reference; otherwise use the email templates and subject-line formulas.
  2. 4 Draft variants Use email-wizard and copywriter patterns to produce the email body and 3 to 5 subject-line options.
03

Verify

Gate, review, validation

  1. 5 Add envelope Attach preview text, CTA, deliverability notes, and A/B test candidates where useful.
  2. 6 Save asset Write single emails, flows, or sequences to their documented email artifact paths.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Automation flow Recommended 
/ak:email flow post-demo nurture for B2B SaaS
Use when:
You need a complete email automation sequence.
Expected:
Loads the flow reference and designs the full automation path.
Drip sequence 
/ak:email sequence 5-day onboarding for trial users
Use when:
A multi-email drip needs copy and sequencing.
Expected:
Produces a full sequence with subject lines, body copy, CTAs, and timing.
Newsletter 
/ak:email newsletter monthly product update
Use when:
You need one newsletter issue.
Expected:
Drafts the newsletter with subject options, preview text, body, and CTA.
Launch email 
/ak:email launch new analytics dashboard
Use when:
A product or feature launch needs campaign copy.
Expected:
Creates launch-oriented copy and A/B-ready subject-line variants.

Handled Scope

  • Newsletters
  • Cold outreach
  • Launch email
  • Nurture sequences
  • Subject-line optimization
  • Deliverability

Artifacts Produced

Email asset

Pattern

single email → assets/copy/emails/{date}-{type}-{slug}.md; flow → assets/emails/flows/{flow-type}-{date}.md; sequence → assets/copy/emails/{date}-{type}-sequence/

Stores campaign copy, automation flow plans, or sequence directories with subject variants, preview text, CTA, timing, and deliverability notes.

Next