← ClaudeAtlas

app-store-metadatalisted

Create, organize, translate, and validate App Store / Mac App Store listing metadata for an Xcode project — localized text (name, subtitle, description, keywords, promo text, release notes, URLs), review information, categories, and screenshot file placement. Use whenever the user wants to write, translate, fix or validate App Store listing text, set up the fastlane metadata structure, or manage multi-language listings ("טקסט לאפסטור", "תתרגם את הליסטינג"). It scaffolds the per-locale files, validates against Apple's limits, and says which steps are website-only. It authors into a hub when there is one and the repo's fastlane/ when there is not — so it is the direct route for a single app, while store-metadata-writer is preferable once a hub holds the profile and both stores must stay consistent. It does NOT upload: delivery to App Store Connect is app-store-deliver's job.
yybd/app-factory · ★ 5 · Data & Documents · score 77
Install: claude install-skill yybd/app-factory
# App Store Metadata (fastlane) > **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 an app listing accepted means every localized field is present, within Apple's character limits, and consistent across languages — and that the things that can't be set programmatically (age rating, pricing, privacy questionnaire) get done on the website. This skill **authors and validates** that metadata; the actual `deliver` upload to App Store Connect is the **`app-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. > **Where the listing copy comes from.** This skill owns the file mechanics — > scaffolding, field placement, and character-limit validation — not the wording, > and not the upload (that's `app-store-deliver`). In the **studio flow** the copy is > lifted from the app's profile (`$APP_HUB/<slug>/profile.md`) by the > `store-metadata-writer` skill, which drives this one; so when a profile exists, > take the copy from there (or let `store-metadata-writer` orchestrate) instead of > re-authoring it here. Standalone (no profi