review-ios-ui

Reviews iOS UI code for HIG compliance, animation quality, haptics, and accessibility via three specialist agents.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/TheMizeGuy/apple-ui-craft-public --skill review-ios-ui-themizeguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-ios-ui
Source: https://github.com/TheMizeGuy/apple-ui-craft-public/tree/main/skills/review-ios-ui
Command: npx skills add https://github.com/TheMizeGuy/apple-ui-craft-public --skill review-ios-ui-themizeguy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? SwiftUI and UIKit code that compiles often still fails Apple's design bar: wrong spring parameters, missing haptics, poor VoiceOver support, wasted iPad layout space, and Dynamic Type breakage. This Skill audits existing iOS UI code against Apple-native quality standards and produces a unified, severity-ranked report. ## Core Features & Use Cases - Parallel specialist review: Dispatches three agents covering visual design (HIG, Liquid Glass, typography, layout), animation and haptics (spring physics, Reduce Motion), and accessibility (VoiceOver, Dynamic Type, contrast, touch targets). - Unified severity-ranked report: Merges and deduplicates findings into per-dimension verdicts (HIG, animation, haptics, accessibility, adaptive layout) with concrete SwiftUI rewrites and top-3 priority actions. - Delta tracking across runs: Writes a review ledger to .claude/apple-ui-craft/last-review.json and reports findings as NEW, RESOLVED, STILL OPEN, REGRESSED, or IMPROVED versus the prior run. - Use Case: After building a new settings screen, run the review on the diff before claiming the work done; it flags a missing Reduce Motion fallback, a 40pt touch target, and a non-adaptive iPad layout with fixes for each. ## Quick Start Ask the assistant to review my iOS UI changes for Apple-native quality, or pass a scope such as a file, directory, "staged", or "all".

Frequently Asked Questions about review-ios-ui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review my iOS UI code for Apple HIG compliance?▼

Run the review on your diff, staged files, a specific file or directory, or the whole project. It dispatches specialists covering HIG, Liquid Glass, typography, navigation, and layout, then returns a unified report with per-dimension verdicts and concrete SwiftUI rewrites.

How to check SwiftUI animations and haptics quality?▼

The animation-haptics-engineer specialist reviews spring parameters, animation purpose, haptic placement, and Reduce Motion handling. Animation and haptics receive independent verdicts (FLUID/ADEQUATE/STIFF/BROKEN and INTENTIONAL/SPARSE/ABSENT/NOISY) in the final report.

Does this review cover VoiceOver and Dynamic Type accessibility?▼

Yes, a dedicated accessibility-engineer specialist reviews VoiceOver, Dynamic Type, contrast, touch targets, and motor accessibility. When accessibility is the entire ask, the documentation recommends using the audit-accessibility skill instead.

What does NOT ASSESSED mean in the review report?▼

NOT ASSESSED means the evidence mode could not reach that dimension, such as task flows or adaptive layout requiring a running sequence or configuration change. It is carried through verbatim rather than promoted to a clean verdict, so it signals an honest coverage gap.

Can I track whether review findings were fixed between runs?▼

Yes, each run writes a ledger to .claude/apple-ui-craft/last-review.json in the reviewed repo. Subsequent runs read it and classify findings as NEW, RESOLVED, STILL OPEN, REGRESSED, or IMPROVED relative to the prior run of the same scope.