asc-aso-audit

1# asc ASO audit
2 
3Run a two-phase ASO audit: offline checks against local metadata files, then keyword gap analysis via Astro MCP.
4When available, include Apple-generated app tags as a discoverability signal.
5 
6## Preconditions
7 
8- Metadata pulled locally into canonical files via `asc metadata pull --app "APP_ID" --version "1.2.3" --dir "./metadata"`.
9- If metadata came from `asc migrate export` or `asc localizations download`, normalize it into the canonical `./metadata` layout before running this skill.
10- For Astro gap analysis: app tracked in Astro MCP (optional — offline checks run without it).
11- For Apple-generated discoverability tags: `asc app-tags list --app "APP_ID" --output json` works when the API returns tags for the app.
12 
13## Before You Start
14 
151. Read `references/aso_rules.md` to understand the rules each check enforces.
162. Identify the **latest version directory** under `metadata/version/` (highest semantic version number). Use this for all version-level fields.
173. The **primary locale** is `en-US` unless the user specifies otherwise.
18 
19## Metadata File Paths
20 
21- **App-info fields** (`subtitle`): `metadata/app-info/{locale}.json`
22- **Version fields** (`keywords`, `description`, `whatsNew`): `metadata/version/{latest-version}/{locale}.json`
23- **App name**: May not be present in exported metadata. If `name` is missing from the app-info JSON, fetch it via `asc apps info list` or ask the user. Do not flag it as a missing-field error.
24 
25## Phase 1: Offline Checks
26…