ios-hig-design

Design native iOS interfaces following Apple Human Interface Guidelines with SwiftUI and UIKit patterns.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/rachmadideni/ai-staff-assistant --skill ios-hig-design-rachmadideni
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ios-hig-design
Source: https://github.com/rachmadideni/ai-staff-assistant/tree/main/.agents/skills/ios-hig-design
Command: npx skills add https://github.com/rachmadideni/ai-staff-assistant --skill ios-hig-design-rachmadideni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing iOS interfaces that feel native requires deep knowledge of Apple's Human Interface Guidelines, and teams often ship apps with broken safe areas, missing Dark Mode support, non-native navigation patterns, or accessibility failures that erode user trust. ## Core Features & Use Cases - HIG Design Framework: Eight structured principles covering layout and safe areas, typography and Dynamic Type, semantic colors and Dark Mode, navigation patterns, native controls, accessibility, SF Symbols, and gestures with haptics. - Scoring and Audit System: Rate any iOS interface or SwiftUI/UIKit code from 0-10 against HIG principles, with a quick diagnostic checklist identifying specific fixes needed to reach 10/10. - Deep Reference Library: Eleven reference documents covering components, keyboard input, privacy permissions, widgets, Live Activities, Siri, Shortcuts, Handoff, and system integration. - Use Case: When building a new iPhone app screen with a tab bar, navigation stack, and form inputs, use this Skill to verify touch targets are 44pt, safe areas are respected, semantic colors support Dark Mode, and VoiceOver labels are complete. ## Quick Start Review my SwiftUI profile screen code against Apple Human Interface Guidelines and score it from 0 to 10 with specific fixes.

Frequently Asked Questions about ios-hig-design

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

FAQPage Schema
How do I design an iOS app that follows Apple Human Interface Guidelines?▼

Follow the eight core principles: respect safe areas and 44pt touch targets, use semantic text styles for Dynamic Type, apply semantic system colors for Dark Mode, use tab bars and navigation stacks instead of hamburger menus, prefer native controls, add VoiceOver labels, use SF Symbols, and never override standard gestures.

What navigation pattern should I use for an iOS app?▼

Use a tab bar with 2-5 primary destinations for top-level structure, NavigationStack for hierarchical drill-down, and modal sheets for focused tasks. Avoid hamburger menus and Android-style patterns, which feel foreign to iOS users.

Does SwiftUI support Dark Mode and Dynamic Type automatically?▼

Yes, when you use semantic colors like Color(.label) and Color(.systemBackground) plus semantic text styles like .title and .body. Hardcoded colors and fixed font sizes break both features, so preview with .preferredColorScheme(.dark) and test at the largest Dynamic Type size.

What is the minimum touch target size on iOS?▼

The minimum touch target is 44 x 44 points for all interactive elements, and it is non-negotiable. In SwiftUI, enforce it with .frame(minWidth: 44, minHeight: 44) on buttons and controls.

How do I make my iOS app accessible with VoiceOver?▼

Add .accessibilityLabel to every interactive element, .accessibilityValue for state, and .accessibilityHint for actions. Group related elements with .accessibilityElement(children: .combine), hide decorative images, and test the complete app flow using only VoiceOver.

When should I request iOS permissions like camera or location?▼

Request permissions just-in-time when the user takes an action requiring them, never at app launch. Show a pre-permission screen explaining the value first, and always provide graceful fallback options when permission is denied.