What problem does it solve? Keeping App Store metadata (names, descriptions, keywords, localizations) consistent between local files and App Store Connect is error-prone when done manually, especially across multiple locales and app versions. ## Core Features & Use Cases - Canonical metadata sync: Pull, edit, validate, and push app-info and version localization fields as JSON files via the asc metadata workflow. - Review and approval flow: Generate review artifacts with asc metadata plan, approve changes selectively, and apply them with confirmation. - Keyword and quick-edit workflows: Diff, import, and sync keywords from CSV files, or apply one-off field updates with explicit version selectors. - Use Case: You are preparing a new release of your iOS app and need to update the description and keywords in five locales. Pull the canonical metadata, edit the JSON files locally, validate against App Store character limits, dry-run the push, then apply. ## Quick Start Ask the assistant to pull the App Store metadata for your app ID and version into a local metadata directory, then validate and push the updated files.
