agentleFS
Sign inStart free
charanjit-singhcharanjit-singh/lovable-skills/skills/pricing-and-billing/SKILL.md

pricing-and-billing

Skill10 starsChanged 6 months agoMITView on GitHub

Use when implementing Stripe subscriptions, checkout, customer portal, trials, invoices, or plan gating. Not for one-time tips without Stripe or display-only pricing tables with no payment.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Never use secret key in frontend.

    line 27
  2. Distinctive:

    After checkout success, wait for webhook before unlocking pro features (or poll subscription row with timeout UX).

    line 28
  3. Distinctive:

    Update DB idempotently; log event id processed.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Pricing and billing (Stripe)

This skill is the entry point for Stripe work. Pair with:

  • stripe-payment-webhooks — handler and event matrix
  • payment-webhook-idempotency — duplicate event safety
  • payment-webhook-testing — Stripe CLI, local debug
  • payment-failed-and-recovery — dunning UX
  • stripe-one-time-payment-webhooks — non-subscription products

Architecture

  • Checkout or Pricing Table for subscribe; Customer Portal for manage/cancel.
  • Webhooks in an edge function are the source of truth for subscription.status.
  • DB: subscriptions(user_id, stripe_customer_id, stripe_subscription_id, status, price_id, current_period_end).

Client

  • Never use secret key in frontend. Publishable key only for Checkout/Elements if needed.
  • After checkout success, wait for webhook before unlocking pro features (or poll subscription row with timeout UX).

Webhook events (handle at minimum)

  • checkout.session.completed
  • customer.subscription.updated
  • customer.subscription.deleted
  • invoice.payment_failed

Update DB idempotently; log event id processed.

Plan gating

const isPro = subscription?.status === "active" || subscription?.status === "trialing";

Gate routes and server policies — UI-only gates are insufficient.

UX

  • Pricing page: clear plan comparison, annual/monthly toggle if offered.
  • Failed payment: banner + link to portal.
  • Trial end: remind before charge when Stripe trial configured.

Avoid

  • Setting is_pro=true from client query params.
  • Missing webhook signature verification.
  • Hardcoding price IDs without env config per environment.

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