メニュー
Use when coordinating the end-to-end release sequence for a prepared SwiftUI app, from final verification through TestFlight or App Store submission.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when auditing a prepared iOS release for App Store or TestFlight submission risk, including metadata, privacy, capabilities, and reviewer-facing behavior.
Use when producing App Store screenshots from real app renders instead of faked CSS mockups, covering the headless simulator export stage, the composition-to-device-sizes stage, and the gotchas that quietly waste hours. Pairs with ios-app-store-optimization, which covers what the screenshots should say.
Use when designing or reviewing an iOS app icon, lightweight brand system, launch assets, screenshot consistency, or App Store-facing visual identity choices.
Use when shaping the conversion strategy for a real iOS App Store listing: positioning, metadata, the listing promise, and the message each visual asset must convey.
Use when establishing or auditing the Apple-platform baseline for an iPhone or iPad interface, especially native conventions, system constraints, and HIG-aligned decisions.
Use after an iOS screen or flow works, when its visual execution, tactile feedback, or optical consistency still feels unfinished.
| name | solo-ios-release-flow |
| description | Use when coordinating the end-to-end release sequence for a prepared SwiftUI app, from final verification through TestFlight or App Store submission. |
Ship with a repeatable loop. Do not improvise the final mile.
app-store-readinessRun app-store-readiness before the upload step. That skill is the go/no-go audit; this skill owns the order of operations. Use ship-ios-build-one-command only for the archive, sign, export, and upload step.
app-store-readinessIf any answer is no, stop and fix that first.