app-store-review

Audit iOS apps against Apple review guidelines and submission requirements.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Roy-wonji/claude-config --skill app-store-review-roy-wonji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-store-review
Source: https://github.com/Roy-wonji/claude-config/tree/main/skills/swift-ios-skills/skills/app-store-review
Command: npx skills add https://github.com/Roy-wonji/claude-config --skill app-store-review-roy-wonji

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you avoid common App Store rejection causes by verifying App completeness, metadata accuracy, privacy requirements, ATT behavior, IAP/StoreKit rules, entitlements, and HIG-aligned UI patterns before you submit.

Core Features & Use Cases

  • Guideline-focused rejection prevention: Cross-checks completeness (no placeholder content), accurate metadata, minimum functionality, public API usage, and submission readiness.
  • Privacy manifest & policy alignment: Reviews PrivacyInfo.xcprivacy requirements, required API reason codes, third-party SDK manifest coverage, and consistency between manifests, privacy nutrition labels, and observed behavior.
  • ATT correctness: Ensures ATT prompting only when cross-app tracking occurs and that timing/purpose strings follow Apple expectations.
  • IAP/StoreKit compliance: Confirms digital content uses In-App Purchase, subscription display rules, restore purchases, and proper StoreKit 2 entitlement handling.
  • EU DMA and capability/entitlement sanity checks: Flags distribution and entitlement issues that commonly trigger review friction.
  • Practical submission workflow: Guides archive/testflight/submission steps and provides an appeal path for resolution-center rejections.

Quick Start

Use app-store-review to audit your upcoming App Store submission (privacy manifest, ATT, IAP, entitlements, and HIG checklist) and produce a prioritized “fix before submit” list.

Frequently Asked Questions about app-store-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent App Store rejection for privacy manifest issues?

Preventing App Store rejection for privacy manifest issues requires validating PrivacyInfo.xcprivacy files, verifying required API reason codes, checking third-party SDK manifest coverage, and aligning privacy nutrition labels with observed app behavior prior to submission.

When do I need ATT consent prompting in my iOS app?

ATT consent prompting in your iOS app is required only when cross-app tracking occurs, and the App Tracking Transparency flow must use precise timing and purpose strings that follow Apple's expectations to avoid compliance rejection.

How do I check StoreKit configuration for in-app purchase compliance?

Checking StoreKit configuration for in-app purchase compliance involves confirming digital content uses In-App Purchase, validating subscription display rules, verifying restore purchases functionality, and ensuring proper StoreKit 2 entitlement handling before App Store archive and submission.

What are the most common App Store review guideline violations for iOS apps?

Common App Store review guideline violations include incomplete placeholder content, inaccurate metadata, minimum functionality gaps, improper public API usage, and entitlement or capability justification issues that create review friction during the iOS submission process.

Can I audit my iOS app submission readiness before archiving in Xcode?

Yes, you can audit iOS app submission readiness before archiving in Xcode by cross-checking completeness, privacy manifest requirements, ATT behavior, IAP rules, entitlements, and HIG-aligned UI patterns to produce a prioritized fix list prior to submission.

Why does my iOS app get rejected for entitlement and capability issues?

iOS apps get rejected for entitlement and capability issues when distribution configurations and capability justifications are missing or mismatched. EU DMA distribution rules and entitlement sanity checks commonly trigger this type of review friction during App Store submission.