Apply iOS/SwiftUI design principles following Apple Human Interface Guidelines when building any iOS UI component. Only execute this when the current project is an iOS project and involves UI-related work. Use this skill for SwiftUI views, UIKit components, or iOS app development. Ensures HIG compliance with Clarity, Deference, and Depth principles, system colors with Dark Mode support, 8pt grid spacing, SF Pro typography with Dynamic Type, and native iOS interaction patterns. Prevents common anti-patterns like fixed text sizes, Dark Mode neglect, and Safe Area violations.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
npx agent-skills-cli listSkill Instructions
name: ios-ui-design-guide description: Apply iOS/SwiftUI design principles following Apple Human Interface Guidelines when building any iOS UI component. Only execute this when the current project is an iOS project and involves UI-related work. Use this skill for SwiftUI views, UIKit components, or iOS app development. Ensures HIG compliance with Clarity, Deference, and Depth principles, system colors with Dark Mode support, 8pt grid spacing, SF Pro typography with Dynamic Type, and native iOS interaction patterns. Prevents common anti-patterns like fixed text sizes, Dark Mode neglect, and Safe Area violations.
iOS UI Design Guide
Overview
Build native iOS interfaces that look professional and follow Apple Human Interface Guidelines (HIG) by applying systematic design principles. This skill provides comprehensive guidelines for SwiftUI-first development with color system, spacing, typography, and component-specific patterns optimized for iOS.
When to Use This Skill
Activate this skill when:
- Building iOS UI with SwiftUI or UIKit
- Creating iOS app screens, views, or components
- Working with iOS development (Swift, SwiftUI, Xcode)
- Receiving requests like:
- "Create a login screen in SwiftUI"
- "Design an iOS settings view"
- "Build a profile card for iOS"
- "Make this iOS UI follow HIG"
- "Style this SwiftUI view"
Do NOT activate for:
- Web development
- Android development
- Backend/server code
- Non-visual iOS tasks
Core Design Philosophy
Follow Apple Human Interface Guidelines (HIG) three principles + Flexible extensions:
HIG Core Principles
- Clarity (λͺ λ£μ±) - Content and functionality clearly visible and understandable
- Deference (μ‘΄μ€) - UI helps content without competing with it
- Depth (κΉμ΄) - Visual layers and motion convey hierarchy and meaning
Flexible Extensions
- Simplicity - Remove unnecessary elements, focus on core features
- Consistency - Use system components, colors, and fonts
- Accessibility-First - Dynamic Type, VoiceOver, WCAG AA compliance, Dark Mode
Framework Priorities
- Primary: SwiftUI (declarative, modern, recommended)
- Secondary: UIKit (complex animations, legacy integration)
How to Use This Skill
Step 1: Load Relevant Reference
Before implementing any iOS UI component, load the appropriate reference file:
Read references/design-principles.md - HIG core principles + Flexible extensions
Read references/color-system.md - System colors, Dark Mode, semantic colors
Read references/spacing-system.md - 8pt grid, Safe Area handling
Read references/typography.md - SF Pro, Dynamic Type, text styles
Read references/component-patterns.md - SwiftUI component best practices
Read references/anti-patterns.md - Common iOS design mistakes
Recommendation: Start with design-principles.md for HIG philosophy, then load component-specific files as needed.
Step 2: Apply Component-Specific Patterns
For each component type, reference the corresponding section in component-patterns.md:
- Button:
component-patterns.mdβ Button section - List:
component-patterns.mdβ List section - Form:
component-patterns.mdβ Form section - Navigation:
component-patterns.mdβ Navigation section - Card:
component-patterns.mdβ Card section - Modal/Sheet:
component-patterns.mdβ Modal section - Search:
component-patterns.mdβ Search section - Image:
component-patterns.mdβ Image section
Step 3: Validate Against Anti-Patterns
Before finalizing implementation, check anti-patterns.md to ensure the design avoids:
- β Fixed text sizes (no Dynamic Type support)
- β Dark Mode neglect (hardcoded colors like
.black,.white) - β Safe Area violations (content hidden by notch/home indicator)
- β Touch targets smaller than 44x44pt
- β Ignoring system components
- β Multiple Primary buttons
Step 4: Ensure System Consistency
Apply the 8pt grid system for all spacing:
- Use only: 4pt (rare), 8pt, 12pt, 16pt, 20pt, 24pt, 32pt, 40pt, 48pt, 64pt
- SwiftUI default
.padding()= 16pt - Reference
spacing-system.mdfor component-specific spacing
Use system colors for automatic Dark Mode:
- Labels:
.primary,.secondary,Color(.tertiaryLabel) - Backgrounds:
Color(.systemBackground),Color(.secondarySystemBackground) - ONE accent color via
.accentColor()or project settings - Reference
color-system.mdfor detailed color usage
Maintain Dynamic Type support (REQUIRED):
- Text styles:
.largeTitle,.title,.title2,.title3,.headline,.body,.callout,.subheadline,.footnote,.caption,.caption2 - NEVER use fixed
.font(.system(size: 24))withoutrelativeTo - Reference
typography.mdfor complete type scale
Resources
references/
Documentation loaded into context as needed to inform design decisions:
- design-principles.md - HIG principles (Clarity, Deference, Depth) + Flexible extensions (Simplicity, Consistency, Accessibility)
- color-system.md - System colors, Dark Mode support, semantic colors, adaptive colors, custom colors with Asset Catalog
- spacing-system.md - 8pt grid scale, Safe Area handling, SwiftUI padding modifiers, component spacing
- typography.md - SF Pro font, Dynamic Type (REQUIRED), text styles, font weights, accessibility
- component-patterns.md - SwiftUI patterns for Button, List, Form, Navigation, Card, Modal, Search, Image, Progress, Badge
- anti-patterns.md - Common iOS mistakes: fixed text, Dark Mode neglect, Safe Area violations, touch targets, system component neglect
Quick Decision Tree
iOS UI Component Request
β
ββ What component? β Load component-patterns.md section
β
ββ What spacing? β Use 8pt grid (spacing-system.md)
β
ββ What colors? β System colors + Dark Mode (color-system.md)
β
ββ What typography? β Dynamic Type text styles (typography.md)
β
ββ SwiftUI or UIKit? β SwiftUI first (unless specific UIKit need)
β
ββ Validation β Check anti-patterns.md
Examples
Good Request Flow:
User: "Create a login form in SwiftUI"
β Read references/component-patterns.md (Form section)
β Read references/spacing-system.md (Form spacing)
β Apply: TextField with .body font (Dynamic Type), 8pt spacing, system colors
β Validate against anti-patterns.md
β Implement with Form { Section { TextField, SecureField, Button } }
Component Implementation Checklist:
- β Spacing uses 8pt multiples
- β Dynamic Type support (.title, .body, etc.)
- β System colors (auto Dark Mode)
- β Safe Area respected
- β Touch targets minimum 44x44pt
- β SwiftUI system components used
- β Single Primary button
- β Accessibility (VoiceOver labels)
SwiftUI Code Examples
β Good: HIG-Compliant Button
Button("νμΈ") {
saveData()
}
.buttonStyle(.borderedProminent)
.controlSize(.large)
β Good: Adaptive Colors
VStack {
Text("μ λͺ©")
.font(.headline)
.foregroundColor(.primary) // Auto Dark Mode
Text("μ€λͺ
")
.font(.body)
.foregroundColor(.secondary)
}
.padding()
.background(Color(.systemBackground))
β Bad: Fixed Sizes, No Dark Mode
Text("μ λͺ©")
.font(.system(size: 24)) // β No Dynamic Type
.foregroundColor(.black) // β No Dark Mode
VStack { }
.ignoresSafeArea() // β Content hidden by notch
Platform-Specific Considerations
Safe Area (CRITICAL)
- Always respect Safe Area for content
- Use
.ignoresSafeArea()only for backgrounds - Test on iPhone with notch/Dynamic Island
Dark Mode (REQUIRED)
- Test in both Light and Dark modes
- Use system colors (never
.black,.whitedirectly) - Define custom colors in Asset Catalog with Light/Dark variants
Dynamic Type (REQUIRED)
- Test with largest accessibility text size
- Use system text styles (
.body,.headline, etc.) - Avoid fixed
.lineLimit()that breaks with large text
Preview Multiple Configurations
struct MyView_Previews: PreviewProvider {
static var previews: some View {
Group {
MyView()
.preferredColorScheme(.light)
.previewDisplayName("Light Mode")
MyView()
.preferredColorScheme(.dark)
.previewDisplayName("Dark Mode")
MyView()
.environment(\.sizeCategory, .accessibilityExtraExtraLarge)
.previewDisplayName("Large Text")
}
}
}
Reference Documentation
More by muheun
View allandroid-ui-design-guide: Apply Android/Jetpack Compose design principles following Material Design 3 when building any Android UI component. Only execute this when the current project is an Android project and involves UI-related work. Use this skill for Compose layouts, Material components, or Android app development. Ensures Material You compliance with Dynamic Color, expressive theming, 4dp grid spacing, Roboto typography with Type Scale, and native Android patterns. Prevents common anti-patterns like hardcoded colors, Dark Mode neglect, and touch target violations.
web-ui-design-guide: Apply modern, professional web UI design principles when building any web UI component. Only execute this when the current project is a web project and involves UI-related work. Use this skill for UI tasks involving buttons, forms, cards, layouts, navigation, or any visual web component. Ensures clean minimal design, neutral color palettes with single accent color, 8px grid spacing, clear typography hierarchy, and subtle visual effects. Prevents common anti-patterns like rainbow gradients, tiny text, and inconsistent spacing.
Execute git commit operations when user requests to commit or push code changes. Use this skill to generate recommended commit messages, perform local commits, or push to remote repositories. Auto-activates for Korean keywords ("컀λ°", "νΈμ") and English keywords ("commit", "push"). Always uses Bash tool for git operations and Claude's natural language processing for message generation.
Linear μ΄μ μμ±/μμ /μ½λ©νΈ κΈ°λ₯μ μ 곡νλ μ€ν¬. νκΈ ν€μλ ("μ΄μ μμ±", "μ΄μ μμ ", "μ½λ©νΈ μΆκ°") λ° μλ¬Έ ν€μλ ("create issue", "update issue", "add comment")λ‘ μλ νμ±ν. Gitmoji κΈ°λ° νκΈ μ λͺ©κ³Ό μ¬μ©μ μΉμΈ νμ μν¬νλ‘μ°λ‘ μΌκ΄λ μ΄μ κ΄λ¦¬λ₯Ό μ§μν©λλ€.
