Use when creating a new App Store Connect app record through browser automation because no public API path is available. Covers driving the New App form, bundle ID selection, SKU, platform, primary locale, and first-time ASC record setup.
Use when auditing App Store metadata for ASO gaps, weak keywords, locale drift, subtitle issues, competitor positioning, or missing metadata after pulling canonical files with asc. Produces actionable keyword and metadata fixes.
Use when tracking App Store Connect build processing, finding the latest uploaded builds, checking TestFlight build availability, or cleaning up old builds with asc.
Use when designing, debugging, or running asc CLI commands. Covers flags, output formats, pagination, authentication, JSON parsing, discovery commands, and safe command patterns for App Store Connect workflows.
Use when translating, generating, validating, or syncing localized App Store metadata such as description, keywords, subtitle, promotional text, or what-is-new across App Store locales.
Use when syncing, validating, migrating, pulling, or pushing App Store metadata between local canonical metadata files and App Store Connect through asc.
Use whenever populating, editing, pushing, pulling, or auditing App Store Connect metadata for this app. The canonical source of truth lives at ./metadata/ as sectioned YAML files - one per ASC section (app info, version, categories, age rating, privacy, pricing, review info, IAP, subscriptions, screenshots…
Use when archiving, exporting, signing, or notarizing macOS apps for Developer ID distribution outside the App Store using xcodebuild and asc notarization workflows.
Use when adjusting territory-specific App Store pricing, purchasing-power parity, subscription price schedules, price imports, or storefront equalization with asc.
Use when preparing, validating, submitting, or troubleshooting an App Store release. Covers asc validate, first-time submission issues, availability, review info, IAP inclusion, screenshots, age rating, App Privacy, and final submit flow.
Use when reconciling App Store Connect subscription or IAP products with RevenueCat products, entitlements, offerings, and packages. Covers ASC-to-RC drift, catalog sync, and offering/package correctness.
Use when automating iOS screenshot capture, framing, localization, upload preparation, or metadata screenshot deployment using simulator, Xcode, Koubou framing, and asc screenshot commands.
Use when setting up or repairing App Store signing: bundle IDs, capabilities, certificates, provisioning profiles, encrypted signing sync, export options, or archive signing failures.
Use when preflighting an App Store submission, running asc validate, checking review readiness, submitting a build, monitoring review status, or diagnosing submission blockers with asc.
Use when submitting or updating a Wall of Apps entry for this app through asc apps wall submit, including app metadata, screenshots, and repository entry details.
Use when defining, validating, running, resuming, or auditing repo-local asc workflow automations in .asc/workflow.json, including release pipelines, CI migration, and repeatable App Store operations.
Use when managing App Store Connect with the asc CLI: authentication, metadata, screenshots, TestFlight, builds, validation, review submission, pricing, subscriptions, signing, analytics, finance, workflows, and Xcode archive/export. Routes narrow tasks to the current asc- skills and uses asc 1.4.0 command surfaces.