Hand it to your agent. Live in an hour.

It could write something that looks like it. Sign-in, webhooks, prorated upgrades and refunds are where generated code breaks quietly, and where a mistake costs money. An agent also copies whatever patterns a codebase already has, the wrong ones included. ShipKit gives it working ones, with the rules written down in CLAUDE.md and AGENTS.md and checked by tests, so your agent's time goes into your product instead.

You are invited to a private GitHub repository. Sign in with GitHub and the invite goes out as soon as the payment clears; signed in another way, you connect your GitHub account from the dashboard with one click. Future releases land in the same repository — add it as a remote and pull.

Either, and both at once. The webhook routes only verify, deduplicate and translate a payload into one internal event; features never import a provider client. PAYMENT_PROVIDER picks who takes new checkouts, and existing subscriptions keep renewing wherever they started.

Because D1 and R2 are bindings, not services with credentials: no connection string, no pool, no S3 keys, and local dev runs the same runtime as production. The trade is that workerd forbids some Node patterns — the template already works around the ones that matter, like runtime-eval MDX.

Each optional feature is a directory plus a handful of one-line registrations — a schema barrel line, a handler import, a nav row. The /delete-feature skill knows the recipe for each, and a CI job runs every recipe on every pull request and fails if one has rotted.

On a small app, close to nothing: Workers, D1 and R2 all have free tiers that cover early traffic, and the only always-on cost is your domain. Email and payments bill per use.