App Store Preflight

Run a two-layer preflight:

1. Canonical ASC validation with asc validate.
2. Local rejection-risk audit using metadata, entitlements, privacy files, screenshots, subscription copy, and rule references.

This skill produces a ship/no-ship report with an ordered remediation plan.

Inputs

Resolve these from .agents/config/product.md, .asc/, metadata/, the Xcode project, or live asc reads before asking the user:

• App ID
• Bundle ID
• Platform: usually IOS
• Primary locale: en-US
• Version: read from metadata/version.yaml, project.yml, or the user’s release target
• Build ID: resolve with asc builds list --app <APP_ID> --output json if needed

Step 1: Tool Health

asc --version
asc doctor
asc auth status

Expected CLI: asc 1.4.0 or newer. If auth is broken, stop and route to asc-cli-usage or apple-developer-auth.

Step 2: Canonical ASC Validation

Run the canonical readiness checks first:

ASC_TIMEOUT=90s asc validate --app "<APP_ID>" --version "<VERSION>" --platform IOS --output markdown
asc validate subscriptions --app "<APP_ID>" --output markdown
asc validate iap --app "<APP_ID>" --output markdown

If a TestFlight build is part of the release:

asc validate testflight --app "<APP_ID>" --build "<BUILD_ID>" --output markdown

For CI/gating checks, rerun with --strict --output json --pretty and preserve the JSON findings.

Use ASC_TIMEOUT=90s for full app validation because screenshot-set fetches can exceed the default timeout. asc validate checks metadata length limits, required fields/localizations, review details, primary category, attached/processed build, encryption declaration, content rights, pricing/territory availability, screenshot presence and dimensions, subscription review readiness, promotional image guidance, and age rating completeness.

Step 3: Local App Store Rule Audit

Load applicable checklists from references/guidelines/by-app-type/:

Then inspect rule files from:

• references/rules/metadata/*.md
• references/rules/subscription/*.md
• references/rules/privacy/*.md
• references/rules/design/*.md
• references/rules/entitlements/*.md

Step 4: Local Project Checks

Run these local checks in addition to ASC validation:

• Metadata: metadata/app-info/, metadata/version/, metadata/privacy.yaml, metadata/review-info.yaml, metadata/age-rating.yaml, metadata/encryption.yaml.
• Screenshots: metadata/screenshots.yaml and every referenced PNG path under metadata/screenshots/.
• Subscription catalog: metadata/subscriptions/*.yaml, active product IDs, review screenshots, intro offer disclosure, and archived SKU exclusion.
• Paywall compliance: full renewal price, duration, auto-renew language, trial terms, Restore Purchases, Terms, Privacy Policy.
• Privacy: the app's Info.plist, PrivacyInfo.xcprivacy if present, permission strings, and data collection claims.
• Entitlements: project entitlements versus actual feature usage.
• Localization: required en-US fields, keywords length, missing locale JSON, stale translations.
• Build metadata: bundle version/build number consistency across Info.plist, Xcode project, and latest ASC build.

Step 5: Output Format

Return this shape:

## App Store Preflight

Status: BLOCKED | READY WITH WARNINGS | READY

### ASC Validate
- App version:
- Subscriptions:
- IAP:
- TestFlight:

### Blocking Issues
- [source] issue
  - Evidence:
  - Fix:
  - Recheck:

### Warnings
- [source] issue

### Passed
- check

### Next Command
`asc ...`

Order findings by release risk. Treat Apple-visible inaccuracies, missing review info, broken subscription disclosure, missing screenshots, unprocessed builds, privacy mismatch, or auth failures as blockers.

Autofix Policy

Safe to patch:

• Metadata typo/length fixes in local metadata files.
• Missing non-secret placeholder fields when the value is discoverable from config.
• Local screenshot manifest paths when files exist.
• Subscription wording in local metadata when it is mechanically derived from metadata/subscriptions/.

Do not auto-fix:

• Pricing decisions.
• Privacy claims not proven by code.
• Legal URLs or support URLs not already configured.
• Deleting or recreating ASC products.
• AppTheme or paywall UI changes unless the user explicitly asks.

After any patch, rerun the affected local rule and the relevant asc validate ... command.