ratings-mechanics

1# Ratings Mechanics
2 
3The rating is an asset with mechanics most developers learn the hard way. This skill covers the
4four rules that aren't obvious from the ASC UI. Prompting *code* lives in
5`generators/review-prompt`; reply *writing* lives in `app-store/review-response-writer` — this
6skill is the strategy layer that tells you when each matters.
7 
8## When This Skill Activates
9 
10- Localizing or expanding into new storefronts ("why does my app show no rating in Japan?")
11- Considering the "reset ratings summary" option on a version release
12- Choosing release options before submitting (phased vs immediate, auto vs manual)
13- Planning a per-market ratings strategy alongside `product/localization-strategy`
14- A bad build or review-bomb is threatening the rating
15 
16## Rule 1: Ratings are per-storefront — they do not travel
17 
18Your 4.8★ from 2,000 US ratings renders as **no rating at all** on the Japanese storefront until
19Japanese users rate the app there. Every storefront starts from zero.
20 
21Consequences:
22 
23- ✅ Entering a new market = re-running the early-days ratings playbook *in that market*: prompt
24  eagerly (within guidelines), localize the prompt moment, reply to every early review.
25- ✅ Weight `requestReview` triggers by storefront maturity — a market with 12 ratings needs the
26  prompt more than the home market with 5,000.
27- ❌ Assuming social proof transfers with the binary. A localized listing with zero local ratings
28  converts like an unknown app, because there it *is* one.
29…