agentleFS
Sign inStart free
ryne2010ryne2010/build-lynx-apps/skills/stripe-best-practices/SKILL.md

stripe-best-practices

Skill1 starsChanged 6 months agoMITView on GitHub

Optional service-domain guidance for Stripe integrations used by Lynx.js apps. Guides API selection, Checkout Sessions, PaymentIntents, Connect, subscriptions, and migrations while keeping payment surfaces separate from Lynx UI implementation guidance.

27 other projects use a version of this, 15 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use vercel-react-best-practices, frontend-design and 3 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.
  • VercelSkill

    vercel-react-best-practices

    React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    Also in 4 projects that use this

  • 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, 7 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 7

    Distinctive

    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:

    Before implementing Stripe code, check official Stripe documentation for the current API version and SDK.

    line 7
  2. Very specific:

    Use this skill for payment architecture and backend/service integration decisions.

    line 11
  3. Distinctive:

    When Stripe is used by a Lynx app surface, keep payment architecture separate from Lynx UI composition:

    line 16
  4. Distinctive:

    Do not put Stripe secret keys, webhook secrets, restricted keys, ephemeral key minting secrets, or PaymentIntent/Checkout privileged …

    line 18
  5. Distinctive:

    Create Checkout Sessions, PaymentIntents, SetupIntents, subscriptions, Connect accounts, and webhook handlers on a trusted backend.

    line 19
  6. Very specific:

    Treat Lynx surfaces as clients that display state, collect allowed user intent, and hand off to hosted/native/web payment surfaces …

    line 20
  7. Distinctive:

    Verify current Stripe docs and SDK/API versions before writing code.

    line 21
  8. Very specific:

    Do not treat Stripe-hosted or embedded payment UI as @dumbooks/lynx-ui components.

    line 23
  9. Distinctive:

    Read the relevant reference file before answering any integration question or writing code.

    line 37
  10. Distinctive:

    When the user's request does not clearly fit a single domain above, consult:

    line 41

“Common” is measured: kept by at least 6 in 10 of the 27 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

Before implementing Stripe code, check official Stripe documentation for the current API version and SDK. Do not rely on copied version notes unless verified for the target project.

Scope for Build Lynx Apps

Use this skill for payment architecture and backend/service integration decisions. Do not treat Stripe-hosted or embedded payment surfaces as @dumbooks/lynx-ui components. Route Lynx app UI composition back to lynx-app-builder and lynx-ui-guidance.

Lynx host/client safety

When Stripe is used by a Lynx app surface, keep payment architecture separate from Lynx UI composition:

  • Do not put Stripe secret keys, webhook secrets, restricted keys, ephemeral key minting secrets, or PaymentIntent/Checkout privileged creation logic in a Lynx bundle.
  • Create Checkout Sessions, PaymentIntents, SetupIntents, subscriptions, Connect accounts, and webhook handlers on a trusted backend.
  • Treat Lynx surfaces as clients that display state, collect allowed user intent, and hand off to hosted/native/web payment surfaces documented by Stripe and the target host.
  • Verify current Stripe docs and SDK/API versions before writing code; payment rules are temporally sensitive.
  • Record the target host surface (native app, web host, embedded web surface, or backend-only flow) before recommending Checkout, Payment Element, native handoff, or webhook architecture.
  • Do not treat Stripe-hosted or embedded payment UI as @dumbooks/lynx-ui components. Compose only the surrounding Lynx-native product UI.
  • For PCI/security claims, cite official Stripe docs and clearly separate planning guidance from launch/legal/compliance approval.

Integration routing

Building...Recommended APIDetails
One-time paymentsCheckout Sessionsreferences/payments.md
Custom payment form or externally hosted payment surfaceCheckout Sessions or Payment Elementreferences/payments.md
Saving a payment method for laterSetup Intentsreferences/payments.md
Connect platform or marketplaceAccounts v2 (/v2/core/accounts)references/connect.md
Subscriptions or recurring billingBilling APIs + Checkout Sessionsreferences/billing.md
Embedded financial accounts / bankingv2 Financial Accountsreferences/treasury.md

Read the relevant reference file before answering any integration question or writing code.

Key documentation

When the user's request does not clearly fit a single domain above, consult:

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