App growth

Paid installs only pay off when the platform can see the event that predicts value (a purchase or subscription, not the install) and the spend is judged against an LTV and target CPA written down first. Apple's, Google's, Meta's and TikTok's own docs are the authority for every API, limit, window and rule in these files. Much of the practice is third-party: [eronred] (ASO and growth playbooks, whose benchmarks are its author's claims), [appeeky] (UA skills built on the paid Appeeky API and MCP server, which needs an Appeeky API key) and [rorkai] (the asc ads CLI) and [ApparenceKit] (a Flutter starter-kit author's posts on Meta ads, paywalls and pricing). Many workflows here depend on that third-party Appeeky API: the weekly Apple Ads ROAS work, the RevenueCat revenue join, creative generation and the Meta and TikTok tool calls. Each file tags third-party bullets and gives both values where they differ from a platform. Store listings, keywords and ratings strategy are aso SKILL.md; builds, releases and the asc CLI are app-store-connect SKILL.md and google-play SKILL.md; purchase code, entitlements, paywalls and subscription webhooks are revenuecat SKILL.md.

Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]