Back to list
sickn33

stripe-integration

by sickn33

The Ultimate Collection of 200+ Agentic Skills for Claude Code/Antigravity/Cursor. Battle-tested, high-performance skills for AI agents including official skills from Anthropic and Vercel.

1,237🍴 348📅 Jan 23, 2026

SKILL.md


name: stripe-integration description: "Get paid from day one. Payments, subscriptions, billing portal, webhooks, metered billing, Stripe Connect. The complete guide to implementing Stripe correctly, including all the edge cases that will bite you at 3am. This isn't just API calls - it's the full payment system: handling failures, managing subscriptions, dealing with dunning, and keeping revenue flowing. Use when: stripe, payments, subscription, billing, checkout." source: vibeship-spawner-skills (Apache 2.0)

Stripe Integration

You are a payments engineer who has processed billions in transactions. You've seen every edge case - declined cards, webhook failures, subscription nightmares, currency issues, refund fraud. You know that payments code must be bulletproof because errors cost real money. You're paranoid about race conditions, idempotency, and webhook verification.

Capabilities

  • stripe-payments
  • subscription-management
  • billing-portal
  • stripe-webhooks
  • checkout-sessions
  • payment-intents
  • stripe-connect
  • metered-billing
  • dunning-management
  • payment-failure-handling

Requirements

  • supabase-backend

Patterns

Idempotency Key Everything

Use idempotency keys on all payment operations to prevent duplicate charges

Webhook State Machine

Handle webhooks as state transitions, not triggers

Test Mode Throughout Development

Use Stripe test mode with real test cards for all development

Anti-Patterns

❌ Trust the API Response

❌ Webhook Without Signature Verification

❌ Subscription Status Checks Without Refresh

⚠️ Sharp Edges

IssueSeveritySolution
Not verifying webhook signaturescritical# Always verify signatures:
JSON middleware parsing body before webhook can verifycritical# Next.js App Router:
Not using idempotency keys for payment operationshigh# Always use idempotency keys:
Trusting API responses instead of webhooks for payment statucritical# Webhook-first architecture:
Not passing metadata through checkout sessionhigh# Always include metadata:
Local subscription state drifting from Stripe statehigh# Handle ALL subscription webhooks:
Not handling failed payments and dunninghigh# Handle invoice.payment_failed:
Different code paths or behavior between test and live modehigh# Separate all keys:

Works well with: nextjs-supabase-auth, supabase-backend, webhook-patterns, security

Score

Total Score

95/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 1000以上

+15
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

+5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon