asc-aso-audit

# asc ASO audit Run a two-phase ASO audit: offline checks against local metadata files, then keyword gap analysis via Astro MCP. ## Preconditions - Metadata pulled locally into canonical files via `asc metadata pull --app "APP_ID" --version "1.2.3" --dir "./metadata"`. - If metadata came from `asc migrate export` or `asc localizations download`, normalize it into the canonical `./metadata` layout before running this skill. - For Astro gap analysis: app tracked in Astro MCP (optional — offline checks run without it). ## Before You Start 1. Read `references/aso_rules.md` to understand the rules each check enforces. 2. Identify the **latest version directory** under `metadata/version/` (highest semantic version number). Use this for all version-level fields. 3. The **primary locale** is `en-US` unless the user specifies otherwise. ## Metadata File Paths - **App-info fields** (`subtitle`): `metadata/app-info/{locale}.json` - **Version fields** (`keywords`, `description`, `whatsNew`): `metadata/version/{latest-version}/{locale}.json` - **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. ## Phase 1: Offline Checks Run these 5 checks against the local metadata directory. No network calls required. ### 1. Keyword Waste Tokenize the `subtitle` field (and `name` if available). Flag any token that also appears in the `keywords` field — it...