asc-localize-metadata

Coordinate ASLC and LLM-assisted translation of App Store metadata across locales.

4|Updated Dec 8, 2019
One-click install
npx skills add https://github.com/Detrous/dotfiles --skill asc-localize-metadata-detrous
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-localize-metadata
Source: https://github.com/Detrous/dotfiles/tree/main/claude/skills/asc-localize-metadata
Command: npx skills add https://github.com/Detrous/dotfiles --skill asc-localize-metadata-detrous

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the translation and synchronization of App Store metadata across locales, reducing manual effort and ensuring consistent localization for descriptions, keywords, What's New, and app information.

Core Features & Use Cases

  • Pull English or source locale metadata from App Store Connect.
  • Translate metadata with LLMs and the asc CLI across multiple locales.
  • Push translated fields back to App Store Connect for version and app-info localizations.
  • Use case: localize an app listing to reach new markets with compliant phrasing.

Quick Start

Start by connecting to ASC, downloading the source locale, translating to target locales, and uploading the localized metadata.

Frequently Asked Questions about asc-localize-metadata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate App Store metadata into multiple locales at once?

You can translate App Store metadata into multiple locales by using LLM-assisted translation alongside the asc CLI. The process coordinates downloading source locale fields, translating them, and pushing the localized metadata back to App Store Connect.

Can I sync localized What's New and app descriptions directly with App Store Connect?

Yes, you can sync localized What's New and app descriptions by downloading version localizations, translating the text, and uploading the fields back to App Store Connect using the asc CLI.

Does this localization approach validate App Store character limits for keywords and subtitles?

Yes, the localization process validates character limits for translated fields like keywords and subtitles. It preserves formatting and uses formal tone guidelines to ensure the translated App Store metadata remains compliant.

What is the best way to avoid accidental overwrites when translating app listing metadata?

To avoid accidental overwrites during app listing translation, the process relies on deterministic IDs and explicit locale handling. This ensures translated metadata is pushed only to the correct target language fields.

Do I need the asc CLI to automate multilingual app store localization?

Yes, the asc CLI is required to automate multilingual App Store localization. It handles the download and upload steps for version and app-info localizations, while LLMs handle the actual translation of the metadata.

Why does my localized app subtitle fail the App Store review process?

Localized app subtitles may fail review if character limits are exceeded or phrasing is non-compliant. This translation process uses formal tone guidelines and validates character limits to prevent such localization errors.