Agent skill · design visual · ehmo
ios-design-guidelines
Apple Human Interface Guidelines for iPhone. Use when building, reviewing, or refactoring SwiftUI/UIKit interfaces for iOS. Triggers on tasks involving iPhone UI, iOS components, accessibility, Dynamic Type, Dark Mode, or HIG compliance.
Why this skill is useful
Provides specific design patterns and guidelines for iOS UI development that the AI wouldn't reliably generate on its own.
What it needs
About 10k tokens when loaded. Last updated 2026-03-19. 481 stars on the source repository.
What this skill does
iOS Design Guidelines for iPhone Comprehensive rules derived from Apple's Human Interface Guidelines. Apply these when building, reviewing, or refactoring any iPhone app interface. --- 1. Layout & Safe Areas Impact: CRITICAL Rule 1.1: Minimum 44pt Touch Targets All interactive elements must have a minimum tap target of 44x44 points. This includes buttons, links, toggles, and custom controls. Correct: Incorrect: Rule 1.2: Respect Safe Areas Never place interactive or essential content under the status bar, Dynamic Island, or home indicator. Use SwiftUI's automatic safe area handling or UIKit's safeAreaLayoutGuide. Correct: Incorrect: Use .ignoresSafeArea() only for background fills, images, or decorative elements — never for text or interactive controls. Rule 1.3: Primary Actions in the Thumb Zone Place primary actions at the bottom of the screen where the user's thumb naturally rests. Secondary actions and navigation belong at the top. Correct: Incorrect: Rule 1.4: Support All iPhone Screen Sizes Design for iPhone SE (375pt wide) through iPhone Pro Max (430pt wide). Use flexible layouts, avoid hardcoded widths. Correct: Incorrect: Rule 1.5: 8pt Grid Alignment Align spacing, padding, and element sizes to multiples of 8 points (8, 16, 24, 32, 40, 48). Use 4pt for fine adjustments. Rule 1.6: Landscape Support Support landscape orientation unless the app is task-specific (e.g., camera). Use ViewThatFits or GeometryReader for adaptive layouts. --- 2. Navigation Impact: CRITICAL Rule 2.1: Tab Bar for Top-Level Sections Use a tab bar at the bottom of the screen for 3 to 5 top-level sections. Each tab should represent a distinct category of content or functionality. Correct: Incorrect: Rule 2.2: Never Use Hamburger Menus Hamburger (drawer) menus hide navigation, reduce discoverability, and violate iOS conventions. Use a tab bar instead. If you have more than 5 sections, consolidate or use a "More" tab. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills ehmo/ios