stripe-subscriptions

andrelandgraf/fullstackrecipes · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/andrelandgraf/fullstackrecipes --skill stripe-subscriptions
0 commentsdiscussion
summary

Complete subscription billing system with Stripe integration, feature flags for plan gating, webhook handling, and billing portal.

skill.md

Stripe Subscriptions

Complete subscription billing system with Stripe integration, feature flags for plan gating, webhook handling, and billing portal.

Prerequisites

Complete these recipes first (in order):

Type-Safe Environment Configuration with better-env

Use better-env config modules for type-safe server/public env access, feature flags, and either-or credential constraints.

curl -H "Accept: text/markdown" https://fullstackrecipes.com/api/recipes/config-schema-setup

Neon + Drizzle Setup

Connect a Next.js app to Neon Postgres using Drizzle ORM with optimized connection pooling for Vercel serverless functions.

curl -H "Accept: text/markdown" https://fullstackrecipes.com/api/recipes/neon-drizzle-setup

Pino Logging Setup

Configure structured logging with Pino. Outputs human-readable colorized logs in development and structured JSON in production for log aggregation services.

curl -H "Accept: text/markdown" https://fullstackrecipes.com/api/recipes/pino-logging-setup

Cookbook - Complete These Recipes in Order

Feature Flags with Flags SDK

Implement feature flags using the Vercel Flags SDK with server-side evaluation, environment-based toggles, and Vercel Toolbar integration.

curl -H "Accept: text/markdown" https://fullstackrecipes.com/api/recipes/feature-flags-setup

Stripe Subscriptions DB Sync

Complete subscription system with Stripe, Vercel Flags for plan configuration, webhook handling for syncing subscription state to Postgres, usage tracking, and billing portal integration.

curl -H "Accept: text/markdown" https://fullstackrecipes.com/api/recipes/stripe-sync
how to use stripe-subscriptions

How to use stripe-subscriptions on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add stripe-subscriptions
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/andrelandgraf/fullstackrecipes --skill stripe-subscriptions

The skills CLI fetches stripe-subscriptions from GitHub repository andrelandgraf/fullstackrecipes and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/stripe-subscriptions

Reload or restart Cursor to activate stripe-subscriptions. Access the skill through slash commands (e.g., /stripe-subscriptions) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.827 reviews
  • Naina Bansal· Nov 11, 2024

    Registry listing for stripe-subscriptions matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Mateo Sharma· Nov 7, 2024

    Solid pick for teams standardizing on skills: stripe-subscriptions is focused, and the summary matches what you get after install.

  • Carlos Zhang· Oct 26, 2024

    We added stripe-subscriptions from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Meera Abebe· Oct 2, 2024

    Keeps context tight: stripe-subscriptions is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Yash Thakker· Sep 21, 2024

    Solid pick for teams standardizing on skills: stripe-subscriptions is focused, and the summary matches what you get after install.

  • Rahul Santra· Sep 17, 2024

    Keeps context tight: stripe-subscriptions is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Meera Choi· Sep 5, 2024

    stripe-subscriptions is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Aisha Abbas· Aug 24, 2024

    stripe-subscriptions fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Dhruvi Jain· Aug 12, 2024

    We added stripe-subscriptions from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Pratham Ware· Aug 8, 2024

    Registry listing for stripe-subscriptions matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 27

1 / 3