stripe-dev
Master orchestrator for Stripe integration development. Routes to specialized skills for: (1) Payments - Payment Intents, Checkout, Elements, Payment Links, (2) Billing - Subscriptions, invoices, usage-based billing, customer portal, (3) Connect - Marketplace/platform payments, connected accounts, onboarding, (4) Treasury - Financial accounts, money movement, issuing cards, crypto onramp, (5) Revenue - Revenue recognition, tax, reporting, Sigma, (6) Money Management - Payouts, refunds, disputes, fraud prevention, balance. Use when implementing any Stripe feature, integrating Stripe APIs, building payment flows, or asking about Stripe architecture.
Works with
---
name: stripe-dev
description: Master orchestrator for Stripe integration development. Routes to specialized skills for: (1) Payments - Payment Intents, Checkout, Elements, Payment Links, (2) Billing - Subscriptions, invoices, usage-based billing, customer portal, (3) Connect - Marketplace/platform payments, connected accounts, onboarding, (4) Treasury - Financial accounts, money movement, issuing cards, crypto onramp, (5) Revenue - Revenue recognition, tax, reporting, Sigma, (6) Money Management - Payouts, refunds, disputes, fraud prevention, balance. Use when implementing any Stripe feature, integrating Stripe APIs, building payment flows, or asking about Stripe architecture.
license: MIT
---
# Stripe Dev - Integration Orchestrator
Master skill that routes to specialized Stripe integration skills. Start here when building any Stripe integration.
## When to Apply
Reference this skill when:
- Starting a new Stripe integration
- Choosing between Stripe products for a use case
- Implementing cross-cutting patterns (webhooks, errors, testing)
- Planning Stripe architecture for a project
## Available Skills
| Priority | Skill | Impact | Use Case |
|----------|-------|--------|----------|
| 1 | stripe-payments | CRITICAL | Accept one-time payments, save cards |
| 2 | stripe-billing | CRITICAL | Subscriptions, invoicing, recurring revenue |
| 3 | stripe-connect | HIGH | Marketplace / platform payments |
| 4 | stripe-money-management | HIGH | Payouts, refunds, disputes, fraud |
| 5 | stripe-treasury | MEDIUM | Embedded finance, card issuing |
| 6 | stripe-revenue | MEDIUM | Tax, revenue recognition, reporting |
## Quick Reference
### Routing by Goal
| Goal | Primary Skill | Also Use |
|------|--------------|----------|
| Accept card payments | stripe-payments | stripe-money-management |
| SaaS subscriptions | stripe-billing | stripe-payments |
| Marketplace payouts | stripe-connect | stripe-money-management |
| Usage-based pricing | stripe-billing | stripe-revenue |
| Embed banking features | stripe-treasury | stripe-connect |
| Multi-party payments | stripe-connect | stripe-payments |
| Fraud prevention | stripe-money-management | stripe-payments |
| Tax automation | stripe-revenue | stripe-billing |
| Financial reporting | stripe-revenue | stripe-money-management |
### Architecture by Stage
- **MVP**: Checkout + Customer Portal + Payment Links
- **Growth**: Payment Element + Webhooks + Stripe Tax
- **Platform**: Connect + Treasury + Revenue Recognition + Sigma
## Cross-Cutting Patterns
For detailed integration patterns: `references/integration-patterns.md`
### SDK Setup
```typescript
import Stripe from 'stripe';
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!);
```
### Webhook Verification
```typescript
const event = stripe.webhooks.constructEvent(
body, sig, process.env.STRIPE_WEBHOOK_SECRET!
);
```
### Idempotency
```typescript
await stripe.paymentIntents.create(
{ amount: 2000, currency: 'usd' },
{ idempotencyKey: `order_${orderId}` }
);
```
### Error Handling
```typescript
try {
await stripe.paymentIntents.create({...});
} catch (err) {
if (err instanceof Stripe.errors.StripeCardError) { /* declined */ }
else if (err instanceof Stripe.errors.StripeRateLimitError) { /* retry */ }
else if (err instanceof Stripe.errors.StripeInvalidRequestError) { /* fix */ }
}
```
### Testing
- CLI: `stripe listen --forward-to localhost:3000/webhooks`
- Cards: `4242424242424242` (success), `4000000000000002` (decline)
- 3DS: `4000002500003155` (required), `4000003800000446` (always)
## Deep Dive References
- `references/integration-patterns.md` - Full-stack architecture, database schemas, multi-product patternsMore Project Management skills
firecrawl-build-onboarding
firecrawl/skills
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
onboard
pbakaus/impeccable
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.

