agentleFS
Sign inStart free
reescalderreescalder/claude-skills/stripe-best-practices/SKILL.md

stripe-best-practices

Skill0 starsChanged 4 months agoMITView on GitHub

Best practices for building Stripe payment integrations

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use frontend-design, pdf and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 5 projects that use this

  • AnthropicSkill

    pdf

    Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 5 projects that use this

  • MicrosoftSkill

    mcp-builder

    Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    use controller properties for Connect (not legacy terms)

    line 40
  2. Distinctive:

    Prefer CheckoutSessions over PaymentIntents when on-session payments

    line 44
  3. Distinctive:

    Prefer Stripe-hosted Checkout over embedded Checkout when default choice

    line 45
  4. Distinctive:

    Prefer embedded Checkout over Payment Element when more control needed

    line 46
  5. Distinctive:

    Prefer dynamic payment methods over explicit payment_method_types when using Payment Element

    line 47
  6. Distinctive:

    Prefer SetupIntents over Sources when saving payment methods

    line 48
  7. Distinctive:

    Prefer Confirmation Tokens over createPaymentMethod/createToken when inspecting card before payment

    line 49
  8. Distinctive:

    Prefer Billing APIs over raw PaymentIntents when subscriptions/recurring

    line 50
  9. Distinctive:

    Prefer direct charges over destination charges when platform wants Stripe to take risk

    line 51
  10. Distinctive:

    Prefer destination charges over direct charges when platform accepts liability

    line 52

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “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

Stripe Best Practices

Best practices for building Stripe payment integrations

Keywords

stripe, payment, checkout, subscription, billing

Intents

  • integrate payment processing
  • handle subscriptions
  • process credit cards

Constraints

Never

  • Charges API
  • Sources API
  • Card Element
  • Payment Element in card-only mode
  • Tokens API (unless specific need)
  • mixing Connect charge types
  • legacy Connect terms (Standard/Express/Custom)

Always

  • latest API/SDK version (unless specified otherwise)
  • advise PCI compliance proof for raw PAN handling
  • use controller properties for Connect (not legacy terms)

Preferences

  • Prefer CheckoutSessions over PaymentIntents when on-session payments
  • Prefer Stripe-hosted Checkout over embedded Checkout when default choice
  • Prefer embedded Checkout over Payment Element when more control needed
  • Prefer dynamic payment methods over explicit payment_method_types when using Payment Element
  • Prefer SetupIntents over Sources when saving payment methods
  • Prefer Confirmation Tokens over createPaymentMethod/createToken when inspecting card before payment
  • Prefer Billing APIs over raw PaymentIntents when subscriptions/recurring
  • Prefer direct charges over destination charges when platform wants Stripe to take risk
  • Prefer destination charges over direct charges when platform accepts liability

Decisions

  • When user wants Charges API: advise migration to CheckoutSessions or PaymentIntents
  • When user wants Card Element: advise migration to Payment Element
  • When recurring revenue / subscription / SaaS: recommend Billing APIs + Checkout frontend
  • When platform / marketplace / Connect: follow integration recommendations, use controller properties
  • When migrating PAN data from another processor: point to migration process
  • When render Payment Element before creating intent: use Confirmation Tokens

References

Converted from UASP format (knowledge skill)

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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