Menu
Use after an iOS screen or flow works, when its visual execution, tactile feedback, or optical consistency still feels unfinished.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 when designing iOS settings screens and trust-sensitive flows involving sync, restore, storage, imports, exports, destructive actions, permissions, and any wording that could cause user confusion or data loss.
| name | ios-interface-polish |
| description | Use after an iOS screen or flow works, when its visual execution, tactile feedback, or optical consistency still feels unfinished. |
Polish is usually not a big redesign. It is a series of small corrections that remove friction and visual hesitation.
Use after the screen works. For information architecture, feature requirements, accessibility compliance, or motion behavior, use the corresponding specialist skill first.
ios-motion-and-microinteractions