Stripe Billing & Subscription Setup

What it does

/stripe-billing is a Cursor slash command. Type it in chat to run a saved workflow: Stripe Billing & Subscription Setup.

Sets up complete Stripe subscription infrastructure: checkout sessions, webhook handlers with signature verification, customer portal, and tier checks.

Checkout sessions, customer portal, webhook handlers, and tier feature gating. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /stripe-billing for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /stripe-billing exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Engineering Kit. It is wired to the Third-Party Integration Lead (integration-engineer) and Senior Backend Architect (backend-architect) agents. Required skills: Stripe Subscriptions & Webhook Handling; REST & API Route Design Patterns; SaaS Architecture Patterns & Multi-Tenancy.

When to use it

• Use when adding paid tiers, pricing tables, or subscription billing to your SaaS.
• Use /stripe-billing when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just wrote marketing copy.

When not to use it

• Do not run /stripe-billing as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. Configure Stripe SDK and environment secret variables
2. Create checkout session API endpoint with customer metadata
3. Implement idempotent Stripe webhook handler with signature verification
4. Add database subscription status tracking and user tier permission helpers

Example usage

Type this in Cursor chat: /stripe-billing Add tiered pricing webhook handler for subscription tier upgrades and downgrades

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: src/app/api/webhooks/stripe/route.ts
• Expected artifact: src/lib/stripe.ts
• Expected artifact: src/db/schema.ts

Best practices

• Keep the prompt specific. /stripe-billing Add tiered pricing webhook handler for subscription tier upgrades and downgrades is the shape: object, constraint, and outcome.
• Let the listed agents work in order: integration-engineer → backend-architect.
• Save outputs in the repo. Chat-only answers evaporate.
• Engineering commands should leave tests or an audit note, not only implementation files.

Common mistakes

• Typing /stripe-billing with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Stripe Subscriptions & Webhook Handling skill that the command depends on.