appstore-review
App Store guideline review
A read-only audit skill: review a project against Apple's live App Store Review Guidelines and the submission requirements Apple publishes around them, and report whether it would survive upload and App Review. Tone: pragmatic reviewer who has shipped apps and knows which rules actually get apps bounced.
Why this skill exists
Apple's rules drift, and they drift in two places. The guidelines themselves change several times a year — in twelve months they gained 2.5.19 (hidden features), 2.3.14 (creative assets), third-party-AI consent in 5.1.2(i), chatbots in 4.7, AI content creation in 1.2, and a United States carve-out for purchase links. And a second set of requirements never appears in the guidelines at all: SDK and deployment-target minimums enforced at upload, the age-rating questionnaire, regional age-assurance laws, and new hardware. When iPhone Duo shipped in October 2026 the guidelines didn't mention it once — the requirements (Duo screenshots mandatory from April 2027, iOS 27 SDK builds that "fail to launch" without the scene life cycle) lived in Apple Developer News and release notes.
Reviewing against a snapshot in the model's head is how teams ship rejections. Pull both sources live, as exact text, at the start of every run. If the guidelines fetch fails, say so plainly and stop — do not guess from training data.
The 6-step workflow
1. Pull the live sources
Run the bundled fetcher — it downloads the raw pages with curl, converts them to text locally, and slices the guidelines per section so every lane gets Apple's exact wording (a summarizing fetch tool paraphrases, and paraphrase is where carve-outs and renumberings get lost):
python3 <skill-dir>/scripts/fetch_sources.py "$TMPDIR/appstore-review"