saasmail: Skill for Claude Code

saasmail Onboarding Wizard

Guide the user through deploying a production saasmail instance to their Cloudflare account. This wizard is deployment-only — it does not set up local development (docs/development.md). Never deploy outside it.

Before You Start

The deployment itself is npx saasmail install (the published saasmail package; source in scripts/saasmail/, described in docs/setup.md). No clone is needed: its state and generated wrangler.jsonc live in ~/.saasmail/<slug>/ (SAASMAIL_HOME overrides), never committed. Only a fork or modified code uses yarn saasmail install from a clone (then every npx saasmail below is yarn saasmail). It creates the resources, generates wrangler.jsonc, migrates, generates the secrets, deploys, wires up Email Routing and Email Sending, and verifies, the same way every time. You choose the inputs, show the user the plan, and interpret failures; the user runs the apply.

What the user is signing up for

Tell the user this before touching anything, so they can back out cheaply:

• ~15 minutes of work, plus DNS propagation (5–15 minutes) if they use Cloudflare Email Sending.
• A few decisions: which hostname the UI runs on (a custom domain or *.workers.dev), which domains receive mail, and which outbound provider (Cloudflare Email Sending, Resend, Bavimail, or Postmark) and from which domains.
• Cost: a Cloudflare Workers Paid plan (about 5 USD/month) is required. saasmail uses Queues, which aren't on the free plan. Email Routing is free; Cloudflare Email Sending is usage-based.

Before the plan

Confirm each of these explicitly — ask, don't assume. If any answer is "no", stop and help them resolve it. The installer re-checks the account, zones and Cloudflare plan itself.

1. Domains on Cloudflare. Any domain they use (UI hostname, inbound, send-from) must be an active zone in their Cloudflare account (dashboard → Add a Site, then switch nameservers at the registrar). A domain that receives mail must be a zone of its own, and must not already have other MX records (the installer stops rather than take over a domain's mail). Without a domain they can use --workers-dev for the UI, but not inbound mail.
2. Workers Paid. If not, send them to https://dash.cloudflare.com/?to=/:account/workers/plans and wait.
3. Tooling. Run node --version: it must be v22 or newer. (Only a clone install needs Yarn and yarn install.)
4. Cloudflare credentials. Run npx saasmail install --plan (step 1 below) and read the result: if it says Run npx wrangler@<version> login first., the user runs exactly that command themselves (it opens a browser): ask them to type it with !. A CLOUDFLARE_API_TOKEN also works (permissions in docs/setup.md); never ask them to paste one into the chat.