Stripe Apps

Builds Stripe Apps from Stripe's bundled guides: discovery interview, Dashboard UI on React 17, script extensions, back-ends with fetchStripeSignature, and the generate-to-upload CLI workflow. Use when building or reviewing an app for the Stripe Dashboard.

CodingPack: Stripe skills78 linesstripe-apps
Author
Source
stripe/ai/skills/stripe-apps @ 119bc4a
License
MIT · Copyright (c) 2024–2025 Stripe

About this skill

What it does

Stripe's Apps skill guides an agent through building, changing or reviewing a Stripe App: UI inside the Stripe Dashboard, script extensions that change how Stripe bills, custom actions for Stripe Workflows, and back-ends that react to Stripe events. SKILL.md is a set of routing tables. One sends capability questions to Stripe's product docs, with a rule to check native features before proposing an extension. The others, together with a paragraph above them, point to twelve bundled references the agent must open before the matching work, then the canonical pages they link, read with stripe docs where possible. For an existing app it first reads the manifest, packages, installed SDK and any local agent instructions.

discovery.md is a short interview: what the app should do, where in the Dashboard it appears (mapped to viewports), private or public, which authentication. extension-types.md describes the five app types. ui-extensions.md lists the constraints that break apps most often: React 17.0.2 in a sandboxed iframe, SDK components only, three import subpaths where the wrong one crashes the view, a declared permission for every API call. script-extensions.md, backend.md (fetchStripeSignature, Secret Store), authentication.md (restricted keys by default), webhooks.md, onboarding-ux.md, publishing.md and canonical-docs.md cover the rest. workflow.md fixes the order: stripe plugin install apps, stripe generate app (never stripe apps create), pnpm install, build, test, stripe apps start, stripe apps upload, install in a sandbox. Its last step and feedback.md have the agent send one stripe feedback report to Stripe per build session.

When to use it, and when not

Use it for a Dashboard panel, a full-page app, a billing script or an event-driven back-end, or to learn whether an extension can meet a billing requirement at all.

Stripe API code outside an app belongs to the best-practices skill. This one needs Stripe CLI 1.52.0 or newer with the Apps plugin, pnpm, and a Stripe account or sandbox.

How to run it

The install command below puts SKILL.md, the references and the licence in place.

  • Claude Code: /stripe-apps, or ask for the skill by name.
  • Codex: $stripe-apps.
  • Cursor: type / in the Agent chat and pick stripe-apps.

Example: /stripe-apps Build a private app that shows a customer's order history from our store on their Dashboard page.

How it differs from similar skills

Stripe integration best practices from the same pack covers the Stripe API in your own code. ChatGPT Apps SDK builds apps for a different host, ChatGPT, on MCP. No other skill in our catalog builds Stripe Apps.

Install

Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.

Claude Code — macOS, Linux
curl -fsSL --create-dirs -o ~/.claude/skills/stripe-apps/SKILL.md https://anymodel.org/en/skills/stripe/stripe-apps/SKILL.md -o ~/.claude/skills/stripe-apps/LICENSE https://anymodel.org/en/skills/stripe/stripe-apps/LICENSE -o ~/.claude/skills/stripe-apps/references/authentication.md https://anymodel.org/en/skills/stripe/stripe-apps/references/authentication.md -o ~/.claude/skills/stripe-apps/references/backend.md https://anymodel.org/en/skills/stripe/stripe-apps/references/backend.md -o ~/.claude/skills/stripe-apps/references/canonical-docs.md https://anymodel.org/en/skills/stripe/stripe-apps/references/canonical-docs.md -o ~/.claude/skills/stripe-apps/references/discovery.md https://anymodel.org/en/skills/stripe/stripe-apps/references/discovery.md -o ~/.claude/skills/stripe-apps/references/extension-types.md https://anymodel.org/en/skills/stripe/stripe-apps/references/extension-types.md -o ~/.claude/skills/stripe-apps/references/feedback.md https://anymodel.org/en/skills/stripe/stripe-apps/references/feedback.md -o ~/.claude/skills/stripe-apps/references/onboarding-ux.md https://anymodel.org/en/skills/stripe/stripe-apps/references/onboarding-ux.md -o ~/.claude/skills/stripe-apps/references/publishing.md https://anymodel.org/en/skills/stripe/stripe-apps/references/publishing.md -o ~/.claude/skills/stripe-apps/references/script-extensions.md https://anymodel.org/en/skills/stripe/stripe-apps/references/script-extensions.md -o ~/.claude/skills/stripe-apps/references/ui-extensions.md https://anymodel.org/en/skills/stripe/stripe-apps/references/ui-extensions.md -o ~/.claude/skills/stripe-apps/references/webhooks.md https://anymodel.org/en/skills/stripe/stripe-apps/references/webhooks.md -o ~/.claude/skills/stripe-apps/references/workflow.md https://anymodel.org/en/skills/stripe/stripe-apps/references/workflow.md
Codex, Cursor — macOS, Linux
curl -fsSL --create-dirs -o ~/.agents/skills/stripe-apps/SKILL.md https://anymodel.org/en/skills/stripe/stripe-apps/SKILL.md -o ~/.agents/skills/stripe-apps/LICENSE https://anymodel.org/en/skills/stripe/stripe-apps/LICENSE -o ~/.agents/skills/stripe-apps/references/authentication.md https://anymodel.org/en/skills/stripe/stripe-apps/references/authentication.md -o ~/.agents/skills/stripe-apps/references/backend.md https://anymodel.org/en/skills/stripe/stripe-apps/references/backend.md -o ~/.agents/skills/stripe-apps/references/canonical-docs.md https://anymodel.org/en/skills/stripe/stripe-apps/references/canonical-docs.md -o ~/.agents/skills/stripe-apps/references/discovery.md https://anymodel.org/en/skills/stripe/stripe-apps/references/discovery.md -o ~/.agents/skills/stripe-apps/references/extension-types.md https://anymodel.org/en/skills/stripe/stripe-apps/references/extension-types.md -o ~/.agents/skills/stripe-apps/references/feedback.md https://anymodel.org/en/skills/stripe/stripe-apps/references/feedback.md -o ~/.agents/skills/stripe-apps/references/onboarding-ux.md https://anymodel.org/en/skills/stripe/stripe-apps/references/onboarding-ux.md -o ~/.agents/skills/stripe-apps/references/publishing.md https://anymodel.org/en/skills/stripe/stripe-apps/references/publishing.md -o ~/.agents/skills/stripe-apps/references/script-extensions.md https://anymodel.org/en/skills/stripe/stripe-apps/references/script-extensions.md -o ~/.agents/skills/stripe-apps/references/ui-extensions.md https://anymodel.org/en/skills/stripe/stripe-apps/references/ui-extensions.md -o ~/.agents/skills/stripe-apps/references/webhooks.md https://anymodel.org/en/skills/stripe/stripe-apps/references/webhooks.md -o ~/.agents/skills/stripe-apps/references/workflow.md https://anymodel.org/en/skills/stripe/stripe-apps/references/workflow.md
Claude Code — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE','references/authentication.md','references/backend.md','references/canonical-docs.md','references/discovery.md','references/extension-types.md','references/feedback.md','references/onboarding-ux.md','references/publishing.md','references/script-extensions.md','references/ui-extensions.md','references/webhooks.md','references/workflow.md') { $p = Join-Path "$HOME\.claude\skills\stripe-apps" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/stripe/stripe-apps/$f" -UseBasicParsing -OutFile $p }
Codex, Cursor — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE','references/authentication.md','references/backend.md','references/canonical-docs.md','references/discovery.md','references/extension-types.md','references/feedback.md','references/onboarding-ux.md','references/publishing.md','references/script-extensions.md','references/ui-extensions.md','references/webhooks.md','references/workflow.md') { $p = Join-Path "$HOME\.agents\skills\stripe-apps" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/stripe/stripe-apps/$f" -UseBasicParsing -OutFile $p }

Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/stripe/stripe-apps/SKILL.md

SKILL.md

Raw

Stripe Apps

Select and read the existing guidance for the user’s task. Product documentation describes what an extension can do; implementation guides describe how to build it. Before recommending an extension or writing code, load the applicable bundled reference files as well as the relevant product documentation. A link or filename in this skill isn’t a substitute for reading its contents.

For a capability question, check native Stripe features and the documented applicability and limitations of the extension. For an implementation request, create or modify working files using the selected guide. For an existing app, inspect its manifest, packages, installed SDK, and local agent instructions before deciding what to change.

Choose the relevant documentation

Use information already supplied by the user or existing app. Read <references/discovery.md> when you need to clarify the app’s requirements, and <references/extension-types.md> for an overview of app architectures. Ask only for missing information that affects the task.

Product capabilities

Use these existing product documents to determine which capability fits and whether the account has the required access. Don’t infer support from an extension’s name or the existence of a scaffold.

Task Read
Select an extension interface and its supported implementation types Extension points and how extensions work
Change how items are included on subscription invoices Item handling extensions
Customize prorations Native proration behavior and prorations extensions
Apply customer balances Customer balance extensions
Calculate discount amounts Discount calculation extensions
Add an action to Stripe Workflows Existing workflow actions, existing custom actions, and how custom actions work
Customize another product’s behavior Follow the selected interface’s product documentation from the extension-point catalog

Implementation guidance

The references/*.md files are bundled with this skill. After selecting the capability, load the applicable files before following their links to supporting documentation. Combine rows when an app needs multiple types. Follow the selected guide’s prerequisites, scaffolding, testing, and debugging instructions.

Task Read
Build or modify any Dashboard UI, including drawers and full-page apps <references/ui-extensions.md>, then each selected component’s current API documentation
Author, test, or debug a script extension <references/script-extensions.md>, then the selected extension point’s implementation guide
Build a custom-action script <references/script-extensions.md> and build a custom action with a script
Build a custom-action remote function Build a custom action with a remote function
Build a self-hosted UI back-end or webhook service <references/backend.md> and <references/authentication.md>; also load <references/webhooks.md> when receiving Stripe events
Store app credentials with the Secret Store API The Secret Store API section in <references/backend.md> and store secrets, including for apps without a self-hosted back-end
Look up APIs, SDK patterns, configuration, or additional extension documentation <references/canonical-docs.md>

Use the UI reference for layout and composition, and current component documentation for import paths, props, and styling APIs. For scripts and remote functions, follow the selected extension’s documentation; UI and self-hosted back-end instructions don’t define their runtime capabilities.

Shared app lifecycle

Read these references when the corresponding task is needed. Reuse existing apps and packages; scaffold only what is missing.

Task Read
Scaffold, build, test, preview, or upload an app <references/workflow.md>, together with the selected implementation guide
Choose authentication for access to Stripe APIs <references/authentication.md>
Receive Stripe events <references/webhooks.md>
Build a first-run setup experience <references/onboarding-ux.md> and the UI reference
Release versions, change installed permissions, or publish to the marketplace <references/publishing.md>
Submit feedback after running app toolchain commands <references/feedback.md>

Load bundled reference files

  1. Use the task tables to select every applicable bundled reference under references/, then open those files with a file-reading tool before starting the corresponding work. For example, UI with a self-hosted back-end needs both UI and back-end guidance; onboarding also needs the UI reference.
  2. Follow relevant pointers to other bundled references inside the files you load, including filenames written as code rather than links. For example, back-end guidance can require authentication guidance, and changing permissions can require publishing guidance. Use this skill’s direct links to locate those files.
  3. Read the canonical documentation required by those references. External documentation supplements the bundled guidance on workflow, layout, and other task-specific decisions.
  • Resolve references/ paths relative to this skill’s directory and bare reference filenames relative to its references/ directory. When reading the hosted skill, fetch the corresponding reference URLs relative to the skill URL.
  • Load only references relevant to the task, and reuse contents already read during the session unless they have changed. A full-stack app doesn’t require every document in the skill.
  • Read canonical pages using the available documentation tools. Prefer stripe docs when available, including for pages that require account access.
  • Use current product documentation and the installed SDK’s types for API contracts and limitations. If an example in a reference disagrees, check the version and follow the applicable canonical documentation.
  • Read any interface-specific agent instructions supplied with an existing or newly generated extension. If none are present, use the linked product and implementation guides.
  • If the documentation doesn’t establish that an extension meets a requirement, state what is unknown or unsupported before proceeding.
  • Keep the work within the user’s request. Report the changes, validation results, and remaining steps relevant to that app.

Connect through AnyModel API

This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.

More from the pack Stripe skills