revenuecat

Set up RevenueCat subscriptions and wire React Native client purchases.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor --skill revenuecat-naopensedoit2-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revenuecat
Source: https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor/tree/main/.local/skills/revenuecat
Command: npx skills add https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor --skill revenuecat-naopensedoit2-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps you implement in-app subscriptions and entitlements using RevenueCat without duplicating billing data in your own database.

Core Features & Use Cases

  • Initial RevenueCat entity setup (seed workflow): Create the RevenueCat project/apps/products/entitlements/offerings/packages needed for a complete purchase flow before client code is written.
  • Client-side subscription lifecycle: Configure react-native-purchases and provide React state/hooks to fetch customer info, load current offerings, purchase packages, and restore purchases.
  • Correct source-of-truth storage: Enforces that RevenueCat is the source of truth for products/offers/prices and discourages building parallel product tables.
  • Platform-aware API key handling: Uses the correct public API key for Test Store vs iOS vs Android vs web so the client behaves correctly across environments.

Quick Start

Run the required RevenueCat seed script in the scripts directory before building any client-side purchase UI.

Frequently Asked Questions about revenuecat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up in-app subscriptions in React Native with RevenueCat?

To set up in-app subscriptions in React Native, you must create your RevenueCat project, products, entitlements, and offerings, then install the client SDK to wire purchase flows and fetch customer info. Always run the required seed script before building any purchase UI.

Do I need to store subscription product data in my own database when using RevenueCat?

You do not need to duplicate subscription product data in your database when using RevenueCat. RevenueCat serves as the single source of truth for products, offers, and prices, and you should derive all subscription details directly from RevenueCat offerings and customer info.

Can I use RevenueCat to handle web app subscriptions alongside iOS and Android?

Yes, you can use RevenueCat to handle web app subscriptions alongside iOS and Android. The setup uses platform-aware public API key handling to ensure the client behaves correctly across Test Store, iOS, Android, and web environments.

What is the correct way to manage entitlements and offerings for a purchase flow?

Managing entitlements and offerings for a purchase flow involves creating specific subscription products, grouping them into packages, and assigning them to offerings within RevenueCat. The client then uses these seeded identifiers to perform entitlement-based access checks.

How do I restore previous in-app purchases using the RevenueCat SDK in a mobile app?

To restore previous in-app purchases using the RevenueCat SDK, you use the provided React state and hooks to call the restore function, which fetches the latest customer info and updates the user's entitlements based on their purchase history.