
Ios Design Guidelines
Apply Apple Human Interface Guidelines while building iPhone UI in SwiftUI or UIKit so navigation, type, and accessibility pass review.
Overview
iOS design guidelines is an agent skill for the Build phase that applies Apple Human Interface Guidelines to iPhone layout, navigation, typography, accessibility, and system integration.
Install
npx skills add https://github.com/ehmo/platform-design-skills --skill ios-design-guidelinesWhat is this skill?
- 10 rule categories from Layout & Safe Areas through System Integration with impact tiers (CRITICAL/HIGH/MEDIUM)
- CRITICAL coverage: touch targets, safe areas, tab-bar navigation, VoiceOver, and permission timing
- SwiftUI and UIKit-oriented examples tied to official Apple HIG reference
- Explicit Never Do list: no hamburger-primary nav, no blocking back swipe, no color-only meaning, no launch permission du
- Dynamic Type, semantic colors, dark mode, and standard gesture protection called out as non-negotiables
- 10 rule categories with impact labels (CRITICAL, HIGH, MEDIUM)
- 6 explicit Never Do rules in the skill README
Adoption & trust: 1.1k installs on skills.sh; 387 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent keeps proposing iOS UI that violates HIG—hamburger nav, fixed type, bad safe areas—and you risk rejection or poor usability.
Who is it for?
Indie developers building or refactoring iPhone apps who want HIG enforcement inside the coding agent loop.
Skip if: Android or cross-platform-only projects with no native iOS UI, or pure brand exploration with no shipping constraints.
When should I use this skill?
Designing or implementing iPhone app UI, reviewing SwiftUI/UIKit for Apple HIG compliance, or fixing navigation and accessibility on iOS.
What do I get? / Deliverables
Implementation advice aligns with Apple’s ten HIG rule categories and Never Do constraints so SwiftUI/UIKit screens feel native and review-ready.
- HIG-aligned layout and navigation recommendations
- Accessibility and Dynamic Type compliance notes
- Component and permission-pattern corrections per category
Recommended Skills
Journey fit
Canonical shelf is Build because the skill encodes implementation rules for iOS screens, components, and system integration. Frontend subphase covers client UI layout, navigation patterns, and platform-native component choices on iPhone.
How it compares
Platform rule checker for Apple HIG, not a Figma kit or generic web responsive layout skill.
Common Questions / FAQ
Who is ios-design-guidelines for?
Solo and indie builders creating native iPhone experiences who need Human Interface Guidelines enforced during agent-assisted UI work.
When should I use ios-design-guidelines?
Use it during Build frontend work on iOS screens, before Ship review when fixing navigation or accessibility gaps, and when auditing agent-generated SwiftUI or UIKit against Apple patterns.
Is ios-design-guidelines safe to install?
Check the Security Audits panel on this Prism page before installing; the skill is documentation-only guidance with no implied network or secret access.
SKILL.md
READMESKILL.md - Ios Design Guidelines
# iOS Design Skill Apple Human Interface Guidelines for iPhone apps — layout, navigation, typography, accessibility, and system integration rules with SwiftUI/UIKit examples. **Reference:** https://developer.apple.com/design/human-interface-guidelines ## Rule Categories | # | Category | Impact | Rules | |---|----------|--------|-------| | 1 | Layout & Safe Areas | CRITICAL | Touch targets, safe areas, thumb zone, screen sizes | | 2 | Navigation | CRITICAL | Tab bars, large titles, back swipe, state preservation | | 3 | Typography & Dynamic Type | HIGH | Text styles, Dynamic Type, UIFontMetrics, SF Pro | | 4 | Color & Dark Mode | HIGH | Semantic colors, contrast, P3 gamut, accent color | | 5 | Accessibility | CRITICAL | VoiceOver, Bold Text, Reduce Motion, Switch Control | | 6 | Gestures & Input | HIGH | Standard gestures, system gesture protection, input methods | | 7 | Components | HIGH | Buttons, alerts, sheets, lists, tab bars, search, menus, SF Symbols | | 8 | Patterns | MEDIUM | Onboarding, loading, launch, modality, feedback | | 9 | Privacy & Permissions | HIGH | Contextual requests, Sign in with Apple, ATT | | 10 | System Integration | MEDIUM | Widgets, App Shortcuts, Spotlight, Live Activities | ## Never Do - Never use hamburger menus — use a tab bar - Never override swipe-from-left-edge back navigation - Never hardcode text sizes — support Dynamic Type - Never use only color to convey information - Never request all permissions at launch - Never place primary actions at the top of the screen (outside thumb zone) - Never clip content under the status bar, home indicator, or Dynamic Island - Never use blocking spinner overlays for loading states - Never show splash screen logos — match the first screen of the app - Never hide the tab bar during navigation within a tab { "version": "1.0.0", "organization": "Platform Design Skills", "date": "February 2026", "abstract": "Apple Human Interface Guidelines for iPhone apps. 67+ rules across 10 categories covering navigation, layout, typography, color, accessibility, gestures, components, patterns, privacy, and system integration. Each rule includes SwiftUI/UIKit examples with correct and incorrect implementations.", "references": [ "https://developer.apple.com/design/human-interface-guidelines", "https://developer.apple.com/design/human-interface-guidelines/designing-for-ios", "https://developer.apple.com/documentation/swiftui", "https://developer.apple.com/documentation/uikit" ] } # iOS Design Rule Sections ## 1. Layout & Safe Areas (layout) **Impact:** CRITICAL **Description:** Correct layout is foundational to every iPhone app. Violating safe areas causes content to be clipped under the status bar, Dynamic Island, or home indicator. Touch targets below 44pt cause mis-taps and frustration. Bottom-of-screen placement for primary actions respects the natural thumb zone. All layouts must adapt across the full range of iPhone screen sizes from iPhone SE to iPhone Pro Max. ## 2. Navigation (nav) **Impact:** CRITICAL **Description:** Navigation defines how users move through an app and directly affects whether they can find features and complete tasks. iOS users expect a tab bar at the bottom for top-level sections, large titles in primary views, and swipe-from-left-edge for back. Violating these conventions forces users to relearn interaction patterns they already know, increasing cognitive load and abandonment. Preserve visible state so users resume by recognition rather than memory. ## 3. Typography & Dynamic Type (type) **Impact:** HIGH **Description:** Typography is the primary way information is communicated in most apps. Supporting Dynamic Type is both an accessibility requirement and an App Store expectation. Users who set larger text sizes depend on apps respecting that preference. Using built-in text styles ensures automatic scaling, proper weight, and consistent hierarchy across the system. ## 4. Color & Dark Mode (color) **Impa