Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

ios-hig-design

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.

wondelai · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add wondelai/skills --skill ios-hig-design

About this skill


name: ios-hig-design description: '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.' license: MIT metadata: author: wondelai version: "1.5.1"

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 improvements needed to reach 10/10.

iOS Design Framework

1. Layout & Safe Areas

Core concept: iOS devices have specific screen dimensions, safe area insets, and hardware intrusions (notch, Dynamic Island, home indicator) that every layout must respect.

Key insights:

  • Design for the smallest screen first (375pt width, iPhone SE)
  • Safe areas protect content from the notch, Dynamic Island, and home indicator---never place interactive elements under them
  • Standard content margins: 16-20pt from screen edges; spacing increments: 8 / 16 / 24pt
  • Minimum touch target and list row height: 44pt

Product applications:

ContextLayout PatternExample
Status bar20pt classic, 44-54pt on Dynamic Island devicesTime, signal, battery area
Navigation bar44pt standard row + ~52pt large title (~96pt total)Back button, title, actions
Content areaFlexible, scrollable, respects safe areaMain app content
Tab bar49pt height, translucent with blur2-5 primary destinations
Home indicator34pt inset at bottomSystem gesture area

Copy patterns:

  • Use VStack { }, which respects safe areas by default
  • Use .ignoresSafeArea() only for backgrounds and decoration, never interactive content
  • Test on multiple sizes, including iPhone SE and Pro Max

See references/navigation.md when laying out chrome---exact nav bar and tab bar dimensions, large-title behavior, and split-view rules.

2. Typography & Dynamic Type

Core concept: iOS uses the San Francisco (SF Pro) typeface with semantic text styles that automatically scale for accessibility via Dynamic Type. Semantic styles give consistent platform hierarchy; Dynamic Type lets users read at their preferred size without breaking layouts.

Key insights:

  • Large Title: 34pt Bold; Title: 17pt Medium; Body: 17pt Regular; Caption: 12-13pt; secondary text: 15pt at 60% opacity
  • Minimum text size 11pt (captions/secondary only)
  • Line height at least 1.3x font size; optimal line length 35-50 characters on mobile
  • Always left-aligned, non-justified text

Product applications:

ContextTypography PatternExample
Screen titles.largeTitle or .title styleLarge title collapses on scroll
Body content.body style, 17ptList items, descriptions
Secondary info.subheadline or .footnoteTimestamps, metadata
Tab labels10pt SF textTab bar item labels
Buttons.body weight semiboldPrimary action text

Copy patterns:

  • Use .font(.title), .font(.body), .font(.caption) instead of hardcoded sizes; @ScaledMetric for custom spacing that scales
  • Prefer weight and color variation over extreme size differences for hierarchy
  • Test all layouts at the largest Dynamic Type size

See references/typography.md when matching a design to exact specs---per-style hex values and the Dark Mode text-color mapping.

3. Color & Dark Mode

Core concept: iOS provides semantic system colors that automatically adapt between light and dark appearances while preserving contrast and hierarchy.

Key insights:

  • Use Color(.label), Color(.secondaryLabel), Color(.systemBackground) instead of hardcoded colors
  • Color(.systemBlue) is the default tint; .systemRed for destructive actions; .systemGreen for success
  • Dark Mode inverts text colors and shifts backgrounds darker while keeping relative hierarchy; accent colors need lower brightness and higher saturation to pop
  • Maintain 4.5:1 contrast in both modes; preview both during development

**Product applicati

Read the complete source ↗