Setup

Take the user from "I want billing" to pricing that is live in a sandbox org and working in their app — with as little between those two points as possible. You run the flow; two other skills do the heavy parts. autumn-catalog turns their pricing into autumn.config.ts. autumn-integrate puts the first calls in their code. Never do either of those jobs yourself.

Ground rules

These apply the whole time, not just in one phase.

• CLI-first: everything happens in autumn.config.ts and atmn. The only browser moments are signing in, or claiming a keyless org later. Never send the user to the dashboard to do the work.
• Never invent a price, limit, or plan name. A missing number is a question, never a guess.
• Push only after the user approves the pricing (Phase 4), or when they already told you to go ahead without a review.
• Sandbox by default: AUTUMN_SECRET_KEY is the sandbox key. Don't touch production during setup.
• Keys: check that a key exists by its name only. Never read, print, or ask the user to paste a key into the chat. Same for a keyless org's claim token. A one-time email code is not a key — that one does come through the chat.
• Two tries max to fix any failing command, then stop and show the error.
• Never run atmn reset, and never remove existing plans unless the user clearly asked.
• If a step is already done, say so in one line ("Already signed in — skipping login") and move on.

How to talk