A build can pass Apple's own validation and then not appear in TestFlight at all, TestFlight being Apple's way of putting an app on your own phone before the public sees it. The reason is that a new app has no tester groups until somebody creates one. Nothing in the code says so. What you buy is that kind of knowledge in two forms: files Claude reads before it acts, and code Claude runs.
The course
15 milestones, each ending in a gate
About 39,000 words, from a Mac with nothing installed on it to an app on sale. A step is finished when a command proves it finished. The gate runs, and its printed output has to show the thing happened: a build that compiled, which is the code turning into a copy of the app a phone can run, or an upload Apple acknowledged. Claude reporting that it went fine does not clear a gate. Beside the milestones sits STATE.md, the course's memory: where you are, what has been decided, what is sitting with Apple. Week three reads it and does not repeat week two.
The errors guide
More than a hundred named failures
About 19,000 words, and every entry is written the same way: the message on your screen, what it actually means, the fix, and what stops it happening again. Most are dated postmortems from apps that shipped. Entries are keyed by the message, so the words in front of you are the words you search for. App Review turns submissions down, including those of people who have shipped before, and the common rejections have their recovery steps written out here.
The guidebook
20 walkthroughs, 28 real screenshots
About 37,000 words, one page for each screen where a person has to click with their own hands. Enrolling as an Apple developer. API keys, the long passwords one program uses to identify itself to another. iCloud containers, and the CloudKit deploy, CloudKit being Apple's sync service and the deploy being the moment its list of data types goes live for real users. The privacy questionnaire. Submission. Stripe for taking money, Cloudflare for putting your site at a real address, GitHub for keeping your code somewhere other than your laptop.
Copied into your project
18 files stamped into your own project
A SwiftUI project scaffold, the skeleton app you start from, with its entitlements already set, meaning the permissions that let features like iCloud work at all, and a privacy manifest, the declaration Apple now requires about the data your app touches. A four-page website: support, privacy, a guide and a front page. Apple requires the first two. Four working documents, among them a submission checklist and a runbook for the day the app goes live. Apple checks all of this. None of it is interesting to write.
Installed into Claude
6 skills, and they ship code
A skill is a folder of instructions Claude loads when the moment calls for it. Six of them, about 15,000 words, each with working code attached. The mentor that runs the course reads STATE.md, works the milestone, runs the gate, and writes the state back before the session ends. A preflight for the copy of your database that Apple runs for real users, which changes only when a human presses Deploy and is where sync quietly goes wrong. A two-layer test harness, one layer hammering your data with random operations to see whether the rules still hold, the other driving the app's screens; Claude assembles those test files into your app from templates. A catalogue of defects in SwiftUI, the modern way an iPhone screen is put together, covering the ones that look right in a screenshot and fail under a thumb. A design pass that turns one conversation about colour into every colour the app draws with, an app icon in the three versions iOS asks for, and font files with their names fixed. And a sweep over your app's text for sentences that read as though a machine wrote them, which exits with an error code and can stop a build.
Installed into Claude
13 scripts, and Claude runs all of them
You never open a terminal. Mac setup. Build, test, package and upload in one command. TestFlight status as a plain table. The gates that guard a release. Several go through App Store Connect's API, the way in for programs rather than for a person filling dozens of web forms: they write the store listing, configure a subscription with a price in every country, and audit a submission for the things that get apps rejected. Two CloudKit developer tools come with them. One asks whether the sync service knows about every kind of record your app saves. The other saves a record and checks that it arrives somewhere else. Three subagent definitions round it out, implementer, scout and workhorse, so your Claude hands the wide reading and the repetitive edits to a fresh copy of itself with its own memory.
Free before you buy
Start Here, the opening hour of the course, is about 3,750 words and free to read now, as a page and as a 14-page PDF.
Updates
Apple moves its screens and changes its rules. Pages and scripts get corrected, you re-download the kit from your library, and the changelog says what changed and when.
Not in the box
The $99 a year Apple charges to publish, and the Claude subscription that does the building. Both are in the table below.
