agentleFS
Sign inStart free
witi-projectswiti-projects/Skills/adding-stripe/SKILL.md

adding-stripe

Skill2 starsChanged 6 months agoMITView on GitHub

Integrate Stripe payments into a web application, including checkout sessions, webhooks, and customer portal. Use when the user says "/adding-stripe", "adding stripe", or asks about adding stripe.

  • Reads credentials
  • Installs packages

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user asks to add payments, billing, subscriptions, or Stripe integration.

    line 8
  2. Very specific:

    Verify the webhook signature using stripe.webhooks.constructEvent.

    line 52
  3. Distinctive:

    Update your database with the subscription status.

    line 54
  4. Distinctive:

    Always verify webhook signatures — never trust unverified payloads.

    line 62
  5. Very specific:

    Use Stripe CLI (stripe listen --forward-to localhost:3000/api/webhooks/stripe) for local webhook testing.

    line 63
  6. Very specific:

    Use stripe.prices.list to fetch prices dynamically instead of hardcoding them.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add Stripe Payments

Use this skill when the user asks to add payments, billing, subscriptions, or Stripe integration.

Steps

  1. Install the SDK

    npm install stripe @stripe/stripe-js

  2. Add environment variables

    STRIPE_SECRET_KEY=sk_test_...
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_test_...
STRIPE_WEBHOOK_SECRET=whsec_...

  3. Create a Stripe client module — create lib/stripe.ts:

    import Stripe from "stripe";

export const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!, {
  apiVersion: "2024-12-18.acacia",
});

  4. Create a checkout API route — create an endpoint that creates a Stripe Checkout session:

    const session = await stripe.checkout.sessions.create({
  mode: "subscription", // or "payment" for one-time
  payment_method_types: ["card"],
  line_items: [{ price: priceId, quantity: 1 }],
  success_url: `${origin}/success?session_id={CHECKOUT_SESSION_ID}`,
  cancel_url: `${origin}/pricing`,
  customer_email: userEmail,
});
return redirect(session.url!);

  5. Create a webhook handler — create a POST endpoint at /api/webhooks/stripe:

    • Verify the webhook signature using stripe.webhooks.constructEvent.
    • Handle key events: checkout.session.completed, customer.subscription.updated, customer.subscription.deleted, invoice.payment_failed.
    • Update your database with the subscription status.
  6. Add customer portal (optional) — create an endpoint that redirects to stripe.billingPortal.sessions.create so users can manage their subscription.
  7. Add pricing page UI — create a pricing page with plan cards that call the checkout API route.

Notes

  • Always verify webhook signatures — never trust unverified payloads.
  • Use Stripe CLI (stripe listen --forward-to localhost:3000/api/webhooks/stripe) for local webhook testing.
  • Store the Stripe customer ID in your user database to avoid creating duplicate customers.
  • Use stripe.prices.list to fetch prices dynamically instead of hardcoding them.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free