revenuecat

Automate RevenueCat setup with seed data and Expo client wiring.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/hajrasarwar11/DataBase-Engine-with-AI --skill revenuecat-hajrasarwar11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revenuecat
Source: https://github.com/hajrasarwar11/DataBase-Engine-with-AI/tree/main/.local/skills/revenuecat
Command: npx skills add https://github.com/hajrasarwar11/DataBase-Engine-with-AI --skill revenuecat-hajrasarwar11

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

RevenueCat setup for Expo/mobile apps can be complex, requiring server-side provisioning, multiple app configurations, and CRUD management of RevenueCat entities. This Skill provides a structured guideline to bootstrap projects, apps, products, entitlements, offerings, packages, and keys, and to tie them to client-side purchases.

Core Features & Use Cases

  • Seed and bootstrap RevenueCat resources using a script (seedRevenueCat.ts) with getUncachableRevenueCatClient, creating a project, test/app stores, products, entitlements, offerings, packages, and test API keys.
  • Client-side integration using react-native-purchases to enable in-app purchases in Expo/mobile apps, with a SubscriptionProvider and useSubscription hook for state.
  • Guidance for environment variables (REVENUECAT_PROJECT_ID, REVENUECAT_TEST_STORE_APP_ID, REVENUECAT_APPLE_APP_STORE_APP_ID, REVENUECAT_GOOGLE_PLAY_STORE_APP_ID) and best practices to avoid hard-coding values.
  • Reference docs and scripts: links to initial setup and subsequent management docs for RevenueCat REST API usage.

Quick Start

Initialize the RevenueCat integration by following the seed script workflow and then wire up the client with RevenueCat in your Expo/mobile app.

Frequently Asked Questions about revenuecat

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

FAQPage Schema
How do I set up RevenueCat in-app purchases for an Expo React Native app?

Bootstrapping RevenueCat in Expo involves running a seed script to automate server-side provisioning of projects, products, and offerings, then wiring the client with react-native-purchases for in-app purchases.

What is needed to bootstrap RevenueCat server-side resources for mobile apps?

Bootstrapping RevenueCat server-side resources requires the RevenueCat REST SDK and a seed script to automate creating projects, app stores, products, entitlements, offerings, packages, and test API keys.

Can I automate RevenueCat provisioning for multiple app stores?

Automating RevenueCat provisioning for multiple app stores uses a seed script to configure test, Apple App Store, and Google Play Store apps, driven by environment variables to avoid hard-coding values.

How does the SubscriptionProvider hook work with react-native-purchases?

The SubscriptionProvider works with react-native-purchases by wrapping your Expo app to manage subscription state, exposing a useSubscription hook to access in-app purchase data.

What environment variables do I need for RevenueCat integration?

RevenueCat integration requires environment variables for project and app IDs, including REVENUECAT_PROJECT_ID, REVENUECAT_TEST_STORE_APP_ID, REVENUECAT_APPLE_APP_STORE_APP_ID, and REVENUECAT_GOOGLE_PLAY_STORE_APP_ID.

Does RevenueCat integration work without hard-coding app IDs in React Native?

RevenueCat integration avoids hard-coding app IDs in React Native by using environment variables for project and store app IDs, keeping configuration dynamic and secure.