メニュー
Use when designing onboarding, first-run, zero-state, or no-data experiences for iOS apps so people understand what the product does, what to do next, and how to reach value quickly without heavy setup friction.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ios-empty-states-and-first-run |
| description | Use when designing onboarding, first-run, zero-state, or no-data experiences for iOS apps so people understand what the product does, what to do next, and how to reach value quickly without heavy setup friction. |
The first useful action matters more than a long explanation.
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.
