How to avoid disaster when vibe-coding a billing engine — Andrew Garvin, Stripe

Generating a billing setup quickly still leaves the business rules to verify. The published account of a Stripe billing talk describes an agent creating a sandbox customer, metered usage and a draft invoice with separate credit pools. Billing carries deep business logic and real money, so the speaker recommends letting an agent speed up work in a test environment and stopping there rather than shipping to production unattended. Rules such as credit expiry, automatic recharge and overage are where hand-built setups tend to go wrong. Skills files carrying the API's hard-won context, and verbose error messages written so an agent can correct itself, help the agent along. The useful role is accelerating construction of something people can inspect and test before it affects real invoices.