移动开发

rc-catalog-management

revenuecat/ai-toolkit

Use this skill when managing the Android product catalog through the Play Console and the RevenueCat dashboard. Covers the two sided catalog flow (create in Play Console, import or map in RevenueCat), entitlement and offering maintenance, and why you do not call the Google Play Developer API directly.

  • 648 次安装
  • 76 星标
  • 收录于

安装命令

npx skills add https://github.com/revenuecat/ai-toolkit --skill rc-catalog-management

SKILL.md

Catalog Management

Manage the Android product catalog across two surfaces: the Google Play Console (source of truth for products) and the RevenueCat dashboard (entitlements, offerings, targeting). You do not call the Google Play Developer monetization.subscriptions or monetization.onetimeproducts endpoints from your app or backend.

Phase 1: Understand

Read this phase before you touch anything.

Why two surfaces

Surface Owns Examples
Google Play Console Underlying products, base plans, offers, prices premium_monthly, base plan p1m, intro offer
RevenueCat dashboard Entitlements, Offerings, Packages, Targeting pro entitlement, default offering, $rc_monthly package

Play Console holds the billable SKU. RevenueCat decides which SKU gets surfaced to which user and under which entitlement key.

What changes without an app update