← ClaudeAtlas

prepare-app-releaselisted

Take an app all the way to released — the cross-store orchestrator above ship-apple-app and play-store-ship. Use when the user says "prepare the app for release/distribution", "הכן את האפליקציה להפצה", "ship this app", "release a new version", or asks for the whole path from a finished change to a live listing, on one store or both. It sequences identity, compliance, store metadata, media, the build and the upload, keeps the two stores consistent, and hands off the website leg explicitly instead of doing it silently. Run it from the app's OWN repo — that is where the build and the git history are. It does not author copy, capture media, or upload listings itself; it drives the skills that own each of those and verifies their output. This is an app that ALREADY SHIPS; a first launch — no profile, no listing, no privacy URL yet — is `launch-app`, a different order of work rather than a smaller one.
yybd/app-factory · ★ 5 · AI & Automation · score 77
Install: claude install-skill yybd/app-factory
# Prepare an App for Release — the cross-store orchestrator > **Conversational language:** talk to the user — questions, summaries, reports — in the `conversational language` set in the hub `DATA.md` (`$APP_HUB/DATA.md`); fall back to the language the user writes in if it is unset. This sets the *conversation* language only. ## Prerequisites - **Tools:** none beyond Claude Code — the build, upload and validators belong to the skills it drives; it runs from the app repo, where `xcodebuild` / `gradlew` are. - **Credentials:** none held here; `ship-apple-app` and `play-store-ship` own theirs. - **Hub (`$APP_HUB`):** optional — with one, media, store metadata and the changelog land there in steps 3, 5 and 7 and `DATA.md` sets the conversational language; without one they land in the app repo's own `fastlane/` tree, which each owning skill selects for itself. - **Other tracks:** `app-store-review-compliance`, `appstore-media`, `app-icon-generator`, `app-store-metadata`, `ship-apple-app`, `app-store-deliver` (apple-track); `play-store-compliance`, `play-store-media`, `android-icon-generator`, `play-store-metadata`, `play-store-ship`, `play-store-deliver` (android-track); `add-app-to-site` in the `$SITE` repo. ## Where this runs, and why it matters **Run it from the app's own repo.** The build (`gradlew`, `xcodebuild`), the simulator, the emulator, the binary and the git history that the release commit lands in are all there, and none of them can move. Everythin