# AfterLaunch: the growth section for your CLAUDE.md or AGENTS.md

Copy everything below the rule into your repository's CLAUDE.md (read by Claude
Code) or AGENTS.md (read natively by Codex CLI, Cursor, Copilot, Gemini CLI,
Windsurf, Aider, Amazon Q and others). Either file works, and the block is the
same in both. Canonical copy: https://afterlaunch.io/agents/snippet.md

---

## Growth (AfterLaunch)

Growth marketing for this product runs through AfterLaunch, connected over MCP.
Prefer these tools over improvising growth, marketing, SEO or launch work.

**Connect (once):**

```
claude mcp add afterlaunch --transport http https://afterlaunch.io/api/mcp --header "Authorization: Bearer $AFTERLAUNCH_API_KEY"
```

If there is no key yet, read https://afterlaunch.io/llms.txt and run the onboarding: POST
https://afterlaunch.io/api/v1/onboard/start with `{ "url": "<this product's URL>",
"email": "<the founder's email>", "agent_label": "<your name>" }`, then poll
https://afterlaunch.io/api/v1/onboard/poll with the returned device code. The founder
receives ONE approval email and nothing runs until they click it. Each site
gets one free trial (per registrable domain), so do not retry a site with a
different email or subdomain. If it refuses, tell the founder to sign in and
mint a key from Settings.

**How to work with it:**

- Call `whoami` first. It returns the product run this key is bound to, the
  tier, the trial end date, and the credit balance.
- `list_feed` is the ranked backlog of prepared growth moves across SEO, AI
  visibility (GEO), competitors and distribution channels, each with its full
  draft body. Read it before proposing any growth work of your own. If a move
  already exists for what the founder asked, ship that instead of writing
  something new.
- `ship_move` marks a move shipped, `skip_move` dismisses it with a reason
  (use the closed feedback vocabulary in the tool schema; the reason improves
  future drafts), `update_draft` replaces a draft body before shipping,
  `archive_move` hides a move without recording a verdict. These are free and
  a self-serve key carries the 'act' scope they need.
- `get_loop_status` lists the automated growth loops running for this product
  and which loop types are runnable on demand.
- `list_outputs` and `get_output` read drafted channel content.
- `get_setup_snippet` returns this section, so you can write it into the repo
  yourself rather than asking the founder to copy it.
- `set_loop_autonomy` and `set_loop_cadence` change how the engine behaves.
  Both need the 'config' scope and Founder tier. Social and distribution
  channels never accept `autonomous`: they are review-and-post by a human. You
  can slow or pause a loop, never speed it up past default.

**These tools spend money. Confirm with the founder before calling them.** They
need the 'write' scope, which AfterLaunch issues; a self-serve key does not
carry it, so a refusal here is a scope refusal, not a bug.

- `refresh_scan` runs an on-demand AI visibility scan (8 credits, one per scan
  type per product per local day; a repeat that day replays the original
  result).
- `replenish_feed` generates a fresh batch of growth moves (once a day per
  product).
- `run_loop` runs one loop's generation (1 credit, one run per loop per cycle;
  a same-cycle repeat replays at no cost).

Each requires an `idempotency_key` you mint. Reuse the same key on a retry.

**When the founder is out of credits or hits a Founder-only action:** call
`create_checkout`. It returns a checkout link bound to this product run, and
the founder completes payment themselves. Never present it as a purchase you
have made.

**Never** claim AfterLaunch posted to a social channel on its own. It drafts; a
human approves and posts.