ios-hig-design

Featured

Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines". Also trigger when building tab bars, navigation stacks, sheets, or modals for iOS, implementing dark mode, or adapting layouts across screen sizes. Covers navigation patterns, accessibility, SF Symbols, and platform conventions. For general UI polish, see refactoring-ui. For affordance design, see design-everyday-things.

Web & Frontend 2,264 stars 230 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# iOS Human Interface Guidelines Design Skill Framework for designing native iOS interfaces that feel intuitive, consistent, and aligned with Apple's design philosophy. Based on Apple's Human Interface Guidelines, the definitive resource for apps that integrate seamlessly with iPhone, iPad, and the Apple ecosystem. ## Core Principle Apple's iOS design philosophy rests on three pillars: **clarity** (every element legible and purposeful), **deference** (the interface never overshadows the content it presents), and **depth** (layering, transitions, and realistic motion convey hierarchy and spatial relationships). **The foundation:** The best iOS apps internalize this philosophy rather than following HIG rules mechanically. Native components, system conventions, and platform consistency aren't constraints---they're the reason iOS users trust and enjoy apps that feel like they belong. ## Scoring **Goal: 10/10.** Score 1 point per satisfied row of the Quick Diagnostic (6 rows), plus up to 4 points for native idiom: +1 semantic colors/text styles throughout (no hardcoded values), +1 system controls over custom reimplementations, +1 standard gestures and meaningful haptics, +1 SF Symbols and correct app-icon shape. Bands: **9-10** = native, accessible, adapts to Dark Mode and Dynamic Type, zero foreign patterns; **5-6** = works but leaks Android idioms or hardcodes color/size; **<=3** = fails safe areas, touch targets, or VoiceOver. Always state the score and the specific impro...

Details

Author
wondelai
Repository
wondelai/skills
Created
8 months ago
Last Updated
2 weeks ago
Language
Shell
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

apple-design

Apple Human Interface Guidelines (HIG) reference for designing or reviewing UI on iOS, iPadOS, macOS, watchOS, visionOS, tvOS. Use when the user asks how a screen, navigation structure, or interaction should be designed to feel native on an Apple platform; whether a design follows Apple's guidelines; which system control to use in SwiftUI/UIKit; how to set a color, font, spacing, or animation; how to design an app icon or pick an SF Symbol; how to use Liquid Glass; or how to design for accessibility — including when the user never says "HIG" or "Apple design guidelines".

0 Updated 6 days ago
tzzs
AI & Automation Listed

impeccable-ios

iOS and iPadOS platform conventions for native apps built with SwiftUI, UIKit, React Native, Expo, or Flutter. Use when building or reviewing iOS UI. Covers Human Interface Guidelines conformance as the governing rulebook, expressing brand through the layer the platform leaves open, and the iOS slop test for controls that read as ported from a website.

3 Updated today
JZKK720
Web & Frontend Listed

review-ios-ui-apple-hig

Review iOS app UI against Apple Human Interface Guidelines and iOS platform conventions. Use when asked for an Apple HIG-based iOS UI, UX, SwiftUI, UIKit, screenshot, simulator, accessibility, Dynamic Type, navigation, layout, controls, color, typography, or platform-conventions review, especially when the user wants critique or prioritized findings grounded in Apple's interface guidance instead of project-specific design docs.

7 Updated 1 months ago
bastos