app-store-submissionlisted

# app-store-submission ## Purpose Take a verified build from "ready to ship" to "uploaded to store with reviewer credentials, metadata, screenshots, and policy URLs filled out." Stop at the human-required final tap. ## When to trigger Trigger on these user phrases. Match loosely. - "submit to App Store" - "publish my app" - "release to TestFlight" - "push to Apple" - "Google Play submission" - "EAS submit" - "ship it" ## Pre-flight refusals The skill refuses to start unless: - `TEST_RESULTS.md` shows tier one, two, and three PASS within the last seventy-two hours. - `SECURITY_AUDIT.md` shows a GREEN verdict within the last seven days. - `app.json` has a valid bundle ID, version, and icon path. - `eas.json` has a production profile. If any check fails, the skill names the failed item and exits. ## Inputs to collect 1. Target platform: `ios`, `android`, or `both`. 2. Distribution channel: `testflight` or `production` (iOS), `internal` or `production` (Android). 3. App Store Connect metadata YAML path (defaults to `store/app-store-metadata.yaml`). 4. Privacy policy URL slug (defaults to project slug). 5. Test reviewer credentials (existing or generate new). ## Behavior ### Step 1: privacy policy - Read or generate `store/privacy-policy.md` from the template. - Push it to `contact.aigniteconsulting.ai/privacy/<slug>.html`. - Record the URL in metadata. ### Step 2: support page - Read or generate `store/support.md` from the template. - Push it to `contact.aigniteco