asc-revenuecat-catalog-sync

1# asc RevenueCat catalog sync
2 
3Use this skill to keep App Store Connect (ASC) and RevenueCat aligned, including creating missing ASC items and mapping them to RevenueCat resources.
4 
5## When to use
6- You want to bootstrap RevenueCat from an existing ASC catalog.
7- You want to create missing ASC subscriptions/IAPs, then map them into RevenueCat.
8- You need a drift audit before release.
9- You want deterministic product mapping based on identifiers.
10 
11## Preconditions
12- `asc` authentication is configured (`asc auth login` or `ASC_*` env vars).
13- RevenueCat MCP server is configured and authenticated.
14- In Cursor and VS Code, OAuth auth is available for RevenueCat MCP. API key auth is also supported.
15- You know:
16  - ASC app ID (`APP_ID`)
17  - RevenueCat `project_id`
18  - target RevenueCat app type (`app_store` or `mac_app_store`) and bundle ID for create flows
19- Use a write-enabled RevenueCat API v2 key when applying changes.
20 
21## Safety defaults
22- Start in **audit mode** (read-only).
23- Require explicit confirmation before writes.
24- Never delete resources in this workflow.
25- Continue on per-item failures and report all failures at the end.
26 
27## Canonical identifiers
28- Primary cross-system key: ASC `productId` == RevenueCat `store_identifier`.
29- Keep `productId` stable once products are live.
30- Do not use display names as unique identifiers.
31 
32## Scope boundary
33- RevenueCat MCP configures RevenueCat resources; it does not create App Store Connect products directly.
34…