Automated summary
Runs a comprehensive pre-submission checklist for App Store Connect to catch common rejection reasons.
Strengths
- Covers multiple Apple guidelines (metadata, IAP, subscriptions, privacy)
- Adapts automatically to monetization model and app configuration
- Identifies blocking issues and provides clear recommendations
Limitations
- Requires browser access to App Store Connect
- Cannot fully verify all code (e.g., payment bypass patterns)
- Depends on available MCPs (e.g., RevenueCat MCP is optional)
Before clicking 'Add for Review' on a new app version, or after a rejection to verify fixes.
For deep code audits or security reviews outside the submission context.
Security analysis
SafeThe skill provides a checklist for reviewing App Store Connect metadata and does not involve any destructive or exfiltration actions. It only instructs to navigate and verify information, which is safe.
No concerns found
How this analysis is madeExamples
Run the App Store Connect pre-flight check for my app to ensure nothing will cause a rejection before I submit for review.I just got rejected by Apple for Guideline 3.1.1. Run the pre-flight check and verify that all IAPs are properly attached and configured.I'm preparing my app for initial release on the App Store. Perform a full pre-submission checklist to catch any metadata or configuration issues.App Store Connect Pre-flight Check
Run a comprehensive pre-submission checklist for App Store Connect to catch common rejection reasons before submitting for review.
When to Use
- Before clicking "Add for Review" on a new app version
- After uploading a new build to verify everything is configured
- When preparing an app for initial release
- After receiving a rejection to verify all issues are fixed
Interactive Setup
The skill starts by asking about your app configuration:
- Monetization model (Free / Paid / Freemium with IAP)
- Paywall implementation (RevenueCat Paywalls / Custom / None)
- iPad support (iPhone only / Universal)
Based on your answers, irrelevant checks are skipped. For example:
- Free apps skip IAP and RevenueCat validation
- iPhone-only apps skip iPad screenshot checks
- RC Paywalls users get dashboard validation instead of code analysis
The skill also auto-detects which MCPs are available:
- Claude in Chrome (required for all checks)
- RevenueCat MCP (optional, falls back to browser if unavailable)
Checklist Items
Validates against Apple's App Review Guidelines:
- Guideline 2.3 - Accurate Metadata
- Guideline 3.1.1 - In-App Purchase
- Guideline 3.1.2 - Subscriptions
- Guideline 5.1.1 - Data Collection
Version Metadata (Guideline 2.3)
- [ ] App name ≤30 characters
- [ ] Screenshots show app in use (not splash/login screens)
- [ ] Screenshots for all required device sizes
- [ ] Screenshots appropriate for 4+ age rating
- [ ] App previews use only actual app footage
- [ ] Description without trademarked terms or pricing
- [ ] Keywords relevant to app
- [ ] What's New describes changes specifically
- [ ] If IAP: Screenshots/description indicate purchase requirements
In-App Purchases (Guideline 3.1.1)
- [ ] All IAPs in "Ready to Submit" status
- [ ] IAPs SELECTED and attached to this version (common rejection!)
- [ ] Review screenshots uploaded for new products
- [ ] Display names and descriptions appropriate for public
- [ ] No alternative payment mechanisms (license keys, QR codes)
- [ ] Loot box odds disclosed (if applicable)
Subscriptions (Guideline 3.1.2)
- [ ] Subscription period ≥7 days
- [ ] Clear description of what subscriber receives
- [ ] Free trial configured via App Store Connect (if offered)
- [ ] Upgrade/downgrade prevents duplicate subscriptions
- [ ] Consumable currencies do not expire
App Review Information
- [ ] Contact information provided and valid
- [ ] Demo credentials provided if login required
- [ ] Demo credentials actually work
- [ ] All new features described specifically in Review Notes
- [ ] Hidden/advanced features explained
Privacy (Guideline 5.1.1)
- [ ] Privacy policy URL in App Store Connect
- [ ] Privacy policy accessible within app (both required)
- [ ] Privacy labels match actual data collection
- [ ] Age rating answered honestly
Code Verification
- [ ] Restore purchases mechanism implemented
- [ ] No alternative payment bypass patterns
- [ ] Trial duration in code matches ASC config
Instructions
- Navigate to App Store Connect for the target app
- Use Claude in Chrome to systematically check each section
- Report findings as a checklist with pass/fail/warning status
- Highlight blocking issues that will cause rejection
- Note optional improvements
Example Output
App Store Connect Pre-flight Check: MyApp v1.0
BLOCKING ISSUES (will cause rejection):
- In-App Purchases: 2 subscriptions not attached to version
- App Review: Sign-in credentials missing (app shows login screen)
WARNINGS (may cause rejection):
- Screenshots: iPad Pro 12.9" 6th gen missing (using 5th gen)
- Metadata: Promotional text empty
PASSED:
- Version metadata complete
- Privacy policy configured
- Age rating set
- Export compliance answered
- Build uploaded and selected
- Contact information provided
Recommendation: Fix blocking issues before submitting.
Navigation Paths
- Version page:
/apps/{app_id}/distribution/ios/version/inflight - Subscriptions:
/apps/{app_id}/distribution/subscriptions - App Information:
/apps/{app_id}/distribution/app-info - Pricing:
/apps/{app_id}/distribution/pricing - App Privacy:
/apps/{app_id}/distribution/app-privacy
Model
Use haiku for speed - this is a checklist validation task, not complex reasoning.
Apple Guidelines Reference
- Guideline 2.3 - Accurate Metadata: https://developer.apple.com/app-store/review/guidelines/#accurate-metadata
- Guideline 3.1.1 - In-App Purchase: https://developer.apple.com/app-store/review/guidelines/#in-app-purchase
- Guideline 3.1.2 - Subscriptions: https://developer.apple.com/app-store/review/guidelines/#subscriptions
- Guideline 5.1.1 - Data Collection: https://developer.apple.com/app-store/review/guidelines/#data-collection-and-storage
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/app-store-connect-pre-flight-check-mma3js5h/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/app-store-connect-pre-flight-check-mma3js5h' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/app-store-connect-pre-flight-check-mma3js5h/download' --output '.skill-downloads/app-store-connect-pre-flight-check-mma3js5h/SKILL.md.part' && mv '.skill-downloads/app-store-connect-pre-flight-check-mma3js5h/SKILL.md.part' '.skill-downloads/app-store-connect-pre-flight-check-mma3js5h/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/app-store-connect-pre-flight-check-mma3js5h/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.