play-store-metadatalisted
Install: claude install-skill yybd/app-factory
# Google Play Store Metadata (fastlane supply)
> **Conversational language:** talk to the user — questions, summaries, reports — in **the language the user writes in** — unless a `conversational language` is set in the hub `DATA.md` (`$APP_HUB/DATA.md`), which overrides it. This sets the *conversation* language only — content/deliverables follow the app's target locales.
Getting a Play listing published means every localized field is present, within
Google's character limits, and consistent across languages — and that the things
that can't be set programmatically (the Data safety form, the content-rating
questionnaire, pricing) get done on the Play Console website. This skill **authors
and validates** that metadata; the actual `supply` upload is the
**`play-store-deliver`** skill.
Guide the user — don't just generate files. Listing copy is a product/marketing
decision; ask for the positioning and translate intent faithfully rather than
inventing claims. Confirm before installing tools or uploading.
> This is the Android counterpart of the **`app-store-metadata`** skill (Apple).
> In the **studio flow**, cross-store coordination belongs to
> `store-metadata-writer` (Hub): it lifts one copy block from the app's profile
> (`$APP_HUB/<slug>/profile.md`), keeps Apple and Play consistent, and
> drives this skill for the Play file mechanics — so when a profile exists, take
> the copy from there, don't independently re-author or translate it here.
> Standalone (no profile): if th