> ## Documentation Index
> Fetch the complete documentation index at: https://docs.senderkit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Authoring

> Draft a template's subject, layout, and copy from a plain-language prompt.

Starting a template from a blank editor is the slow part. **AI authoring** lets you
describe the message you want in plain language and get back a complete first draft —
subject, layout, copy, and a typed list of the [variables](/concepts/variables) it
uses — which you then refine in the editor before publishing.

## What it produces

You give it a channel and a brief ("a friendly welcome email for a new SaaS signup
with a button to set up their workspace"), and it drafts channel-appropriate content:

* **Email** — a subject line, an optional preheader, a structured body of
  headings, paragraphs, buttons, lists, and dividers, and optionally a
  **color palette** (accent for buttons/links, heading, and body text colors).
  Colors are applied only when the brief mentions a color, brand, or look/feel;
  otherwise the email keeps its neutral defaults.
* **SMS** — a single message body, kept within SMS length budgets.
* **Push** — a short title and body.

Alongside the content it declares the [variables](/concepts/variables) it used —
snake\_case names, types, descriptions, and example values — and reuses variables
you've already defined when they fit, so you're not left wiring up placeholders by
hand.

## Where it fits in the workflow

AI authoring is available in two places:

* **Dashboard editor** — the **Write with AI** button in the template editor
  drafts or rewrites a template inline. Nothing goes live until you review and
  **publish**.
* **MCP server** — the [`senderkit_templates_create`](/mcp/tools#senderkit_templates_create)
  and [`senderkit_templates_regenerate`](/mcp/tools#senderkit_templates_regenerate) tools
  let an AI agent (Claude, Cursor, etc.) generate templates from a brief.
  Both tools save the result as a **draft** and return a link to the editor for
  review — publishing is always a deliberate human step.

In both cases the draft is a new template [version](/concepts/versioning); it
only affects real sends once you publish it.

## What to expect

Treat the output as a strong first draft, not a finished template:

* **Review the copy** — it's a starting point; tighten it to your voice.
* **Check the variables** — confirm the names and types match the data you'll actually
  pass at send time.
* **Then publish** — the draft only affects real sends once you publish it as the
  current version.

<CardGroup cols={2}>
  <Card title="Templates" icon="file-lines" href="/concepts/templates">
    Where authored drafts live.
  </Card>

  <Card title="Versioning" icon="code-branch" href="/concepts/versioning">
    The draft is a version — publish it to go live.
  </Card>
</CardGroup>