agentleFS
Sign inStart free
tarunyadav1tarunyadav1/ios-app-lifecycle/skills/ios-monetization/SKILL.md

ios-monetization

Skill1 starsChanged 36 days agoMITView on GitHub

Add and verify in-app purchases and subscriptions in an iOS app with RevenueCat or StoreKit 2 — products, offerings, entitlements, paywalls, restore, sandbox and StoreKit-config testing, and revenue metrics. Use for "add a paywall", "set up subscriptions", "RevenueCat", "StoreKit", "why isn't my purchase working", or pricing questions.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the project already uses RevenueCat (import RevenueCat, Purchases.configure) or StoreKit 2 directly, stay with it.

    line 10
  2. Distinctive:

    If the RevenueCat MCP is connected, use it to read and create projects, products, entitlements and offerings, and to pull metrics.

    line 12
  3. Distinctive:

    Write down (and confirm with the user) before writing any code:

    line 16
  4. Very specific:

    Create a single @Observable purchase/entitlement store as the source of truth.

    line 27
  5. Very specific:

    Add a StoreKit configuration file (.storekit) synced from App Store Connect, and select it in the scheme for local testing (purchase, …

    line 34
  6. Distinctive:

    Verify: first purchase, restore on a fresh install, upgrade/downgrade between plans, expiry, refund revokes access, and offline launch …

    line 36

≈ “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

iOS Monetization

1. Decide the stack

  • If the project already uses RevenueCat (import RevenueCat, Purchases.configure) or StoreKit 2 directly, stay with it.
  • For a new setup, recommend RevenueCat when the user wants dashboards, paywall experiments or cross-platform support. Recommend plain StoreKit 2 when they want no third-party dependency.
  • If the RevenueCat MCP is connected, use it to read and create projects, products, entitlements and offerings, and to pull metrics. Confirm before any change in the dashboard.

2. Model the catalog

Write down (and confirm with the user) before writing any code:

  • Products: identifiers like <app>.pro.monthly and <app>.pro.annual; type (auto-renewable, non-consumable, consumable); price tier; trial or intro offer.
  • Entitlements: what each product unlocks (usually one pro entitlement).
  • Offerings: the default offering, plus any experiment offerings.

Product IDs are permanent in App Store Connect. Double-check spelling before the user creates them.

3. Implement

  • Configure the SDK once at app launch, with the public API key read from the xcconfig (never a secret key in the app).
  • Create a single @Observable purchase/entitlement store as the source of truth. Views read isPro from it; nothing else checks receipts.
  • Listen for transaction updates (Transaction.updates or the RevenueCat customer-info stream) so renewals, refunds and Family Sharing are reflected live.
  • Paywall must show: price per period in the user's locale (use the product's localized price — never hard-code it), trial terms, what's included, Restore Purchases, and links to Terms of Use and Privacy Policy.
  • Gate features in the model, not with scattered if isPro checks across the view hierarchy.

4. Test before shipping

  • Add a StoreKit configuration file (.storekit) synced from App Store Connect, and select it in the scheme for local testing (purchase, cancel, renew, refund, Ask to Buy).
  • Then test in Sandbox with a sandbox Apple Account on a device, and on TestFlight.
  • Verify: first purchase, restore on a fresh install, upgrade/downgrade between plans, expiry, refund revokes access, and offline launch keeps access.

5. After launch

Pull MRR, trial conversion, churn and refund rate (RevenueCat MCP or the dashboard). Suggest one experiment at a time: price, trial length, or paywall placement. Never change live prices without the user's explicit approval.

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