20 Claude Code subagents tuned for Next.js + Supabase + Stripe. Stop writing generic prompts. Drop in battle-tested agents that know your exact stack.
One-time payment Β· Lifetime updates Β· 14-day refund
npx claude-subagents-pack init
"Ok Claude, wire up Stripe checkout. Remember to verify webhook signatures. Don't use edge runtime. Use integer cents. Store stripe_customer_id on first authβ¦"
"Wait, did it enable RLS? Does it have a `with check`? Did it put the price ID in components again?"
This pack is the muscle memory you've been re-typing into every project. Except it's done right, once, and every agent double-checks the mistakes you keep catching in review.
Each agent comes with operating procedure, code templates, hard rules, and a verification checklist.
auth-setup β Clerk + middleware + Supabase JWTauth-protected-route β route guards + role gatinguser-profile β profile CRUD + avatar uploadsupabase-schema β migrations + type gensupabase-rls β idempotent policiessupabase-seed β deterministic fixturessupabase-realtime β live subscriptionsstripe-setup β client + webhook + catalogstripe-subscription β full subscription lifecyclestripe-checkout β one-time purchasesstripe-webhook-handler β typed, idempotent handlersstripe-customer-portal β self-service billingstripe-refund β refund + entitlement revokeresend-transactional β React Email + helpersresend-welcome β onboarding sequencevercel-deploy β pre-deploy gatemonitoring-setup β Sentry + PostHogapi-rate-limit β Upstash rate limitingtesting-setup β Vitest + Playwrightseo-metadata β OG, sitemap, robots, JSON-LD/new-feature
/add-payment
/debug-webhook
/check-rls
/ship
Not a vibes-prompt. A spec with hard rules and a verification checklist.
---
name: stripe-setup
description: Scaffold Stripe integration β client, webhook endpoint with
signature verification, product catalog, local testing setup.
tools: Read, Edit, Write, Glob, Grep, Bash
---
You are a senior payments engineer. You treat Stripe webhooks as the source
of truth for subscription state, never the client-side redirect. You verify
every signature. You store money as integer cents.
## Hard rules
- Never trust client-side redirect URLs to confirm payment. Wait for webhook.
- Never JSON.parse(body) before signature verification.
- Always make webhook handlers idempotent β Stripe retries.
- Never hardcode price IDs in components. Route through STRIPE_CATALOG.
- Use `nodejs` runtime for the webhook β Edge can't read raw body reliably.
## Verification
- [ ] pnpm build passes
- [ ] curl -X POST /api/webhooks/stripe -d '{}' returns 400 (no signature)
- [ ] stripe trigger checkout.session.completed returns 200
- [ ] .env.example has all three keys
- [ ] lib/stripe/catalog.ts is the only place price IDs appear
Step-by-step walkthroughs you can follow along with. Great for learning the Pack and for video demos.
Add payments to a fresh project in 15 min. 3 agent calls.
Audit every table, fix bad policies, verify with simulated queries.
Schema β RLS β Actions β UI β test. One command.
Resend + React Email + 3-step onboarding drip.
Env, secrets, migrations, build β one command go/no-go.
No tiers. No "contact sales". Lifetime updates.
Everything you see on this page. Forever.
npx claude-subagents-pack init)No. Boilerplates give you the scaffold. This gives Claude Code the muscle memory to build on top. Use both.
The stack specificity is the value. Agents assume Next.js App Router. Other frameworks are roadmap, not launch.
Clerk-first at launch. Supabase Auth variant planned based on demand.
Stripe only at launch.
14-day full refund as long as you haven't committed the output to a public repo.
Ship your next SaaS feature in half the Claude Code turns.
Get the Pack β $39