rejection-handler

# App Store Rejection Handler Guide developers through handling App Store rejections — from understanding why the rejection happened, to crafting effective responses, to escalating when appropriate. ## When This Skill Activates Use this skill when the user: - Says their app was rejected by App Review - Asks for help understanding a rejection notice - Wants to prepare a submission to minimize rejection risk - Needs help writing a response in Resolution Center - Wants to appeal a rejection decision - Asks about common App Store rejection reasons - Mentions "App Review", "guideline violation", or "rejection" - Wants a pre-submission audit for guideline compliance ## Reference Files Before handling a rejection, load: | File | Purpose | |------|---------| | **common-rejections.md** | Top 20 rejection reasons with fixes and response templates | ## Pre-Submission Audit Checklist Run through this before submitting to avoid the most common rejections. Each item maps to a specific App Store Review Guideline. ### App Completeness (Guideline 2.1) - [ ] App launches without crashing on all supported devices - [ ] All features described in metadata are functional - [ ] No placeholder content (lorem ipsum, test data, TODO screens) - [ ] No broken links or dead-end navigation - [ ] All buttons and interactive elements work - [ ] Demo/test accounts provided in App Review notes if login is required - [ ] Beta or test labels removed from UI and metadata ### Accurate Metadata (Guideli...