菜单
Use when deciding how an iPhone or iPad app should be organized, including tab bars, drill-down flows, sheets, settings grouping, information architecture, and navigation patterns that should feel native on iOS.
用 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-navigation-and-ia |
| description | Use when deciding how an iPhone or iPad app should be organized, including tab bars, drill-down flows, sheets, settings grouping, information architecture, and navigation patterns that should feel native on iOS. |
Users should understand where they are, how they got there, and how to leave.
