メニュー
Use when auditing an iOS interface for accessibility, including Dynamic Type, contrast, VoiceOver clarity, hit targets, reduced motion, and interaction patterns that need to remain usable for a wider range of people.
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 | ios-accessibility-design-review |
| description | Use when auditing an iOS interface for accessibility, including Dynamic Type, contrast, VoiceOver clarity, hit targets, reduced motion, and interaction patterns that need to remain usable for a wider range of people. |
Accessibility is part of product quality, not a separate pass.
If the flow only works for visually precise, fully sighted, calm conditions, it is not ready.
