القائمة
Use when auditing a prepared iOS release for App Store or TestFlight submission risk, including metadata, privacy, capabilities, and reviewer-facing behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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 | app-store-readiness |
| description | Use when auditing a prepared iOS release for App Store or TestFlight submission risk, including metadata, privacy, capabilities, and reviewer-facing behavior. |
Submission quality is product quality plus review hygiene.
This is the submission audit gate. It does not archive, upload, or release the build. Use solo-ios-release-flow for the release sequence and ship-ios-build-one-command for the archive-to-upload operation.
If a reviewer or first-time user could misunderstand what the app does, the submission is not ready yet.
