Skills ios-application-dev
📱

ios-application-dev

Safe

Build Production-Ready iOS Apps with UIKit and SwiftUI

Creating iOS interfaces requires understanding Apple platform conventions, accessibility standards, and proper UI patterns. This skill provides comprehensive guidance on building apps that meet Apple Human Interface Guidelines.

Supports: Claude Codex Code(CC)
🥉 76 Bronze
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

Toggle on and start using

Test it

Using "ios-application-dev". Create a settings screen in SwiftUI with email and password fields

Expected outcome:

A complete SwiftUI settings screen with Form, Section grouping, TextField for email with keyboard type and autocapitalization settings, SecureField for password, and Sign In button with disabled state when fields are empty.

Using "ios-application-dev". Add accessibility to a list of products in UIKit

Expected outcome:

UIKit table view cell configuration with accessibilityLabel describing product name and price, accessibilityHint for tap action, and trait settings for button behavior. Includes Dynamic Type support with UIFontMetrics scaling.

Using "ios-application-dev". Implement Dark Mode in an existing UIKit app

Expected outcome:

Guide to replacing hardcoded colors with semantic system colors (.systemBackground, .label, .secondaryLabel), creating asset catalog variants for custom colors, and testing the automatic Dark Mode adaptation.

Security Audit

Safe
v1 • 4/16/2026

All 674 static analyzer findings are false positives. The scanner misidentifies markdown inline code delimiters (backticks) as shell commands, Swift enum values like .hierarchical as crypto algorithms, and standard Swift guard statements as system reconnaissance. This is a legitimate iOS development reference guide containing only documentation and example code with no security risks.

10
Files scanned
3,971
Lines analyzed
0
findings
1
Total audits
No security issues found
Audited by: claude

Quality Score

45
Architecture
100
Maintainability
87
Content
50
Community
100
Security
91
Spec Compliance

What You Can Build

Scaffold iOS Screen Layouts

Generate complete screen implementations with proper safe area handling, touch targets, and semantic layouts following Apple guidelines.

Implement Accessibility Features

Add VoiceOver labels, Dynamic Type support, and Reduce Motion compatibility to existing iOS interfaces.

Review iOS Code Quality

Validate Swift code against Apple best practices for protocols, error handling, and UI implementation patterns.

Try These Prompts

Create UIKit Screen
Create a [screen type] screen in UIKit with SnapKit. Include [components]. Follow 44pt touch target minimum, support Dynamic Type, and use semantic colors for Dark Mode support.
Build SwiftUI View
Build a SwiftUI [view type] with [functionality]. Use NavigationStack for navigation, apply semantic colors, and ensure accessibility labels are present.
Add Accessibility Support
Add VoiceOver accessibility support to [component]. Include proper accessibilityLabel, accessibilityHint, and trait configuration. Support Dynamic Type up to accessibility sizes.
Implement Navigation Flow
Design navigation flow for [feature]. Use TabView for main sections, NavigationStack for drill-down, and .sheet for focused tasks. Preserve state across navigation.

Best Practices

  • Use semantic system colors (.systemBackground, .label) instead of hardcoded RGB values to automatically support Dark Mode
  • Implement 44pt minimum touch targets and 8pt spacing grid for consistent, accessible layouts across all screen sizes
  • Respect user accessibility preferences by using @Environment values for Dynamic Type, Reduce Motion, and Bold Text

Avoid

  • Avoid hardcoding screen widths or assuming fixed device sizes - use safe areas and flexible layouts that adapt to all iPhone sizes
  • Do not use hamburger menus or override system back swipe gestures - follow platform conventions for navigation
  • Never request permissions at app launch without context - request permissions when user actually needs the feature

Frequently Asked Questions

What is the minimum touch target size for iOS?
44x44 points for all interactive elements. This ensures buttons and controls are accessible to all users, including those with motor impairments.
How do I support Dynamic Type in UIKit?
Use UIFont.preferredFont(forTextStyle:) with adjustsFontForContentSizeCategory = true, or UIFontMetrics for custom fonts to scale properly with system text size settings.
Should I use UIKit or SwiftUI for new iOS projects?
SwiftUI is recommended for new projects when targeting iOS 14+. UIKit remains valuable for complex custom interfaces or when supporting older iOS versions.
How do I handle Dark Mode in my app?
Use semantic system colors (.systemBackground, .label) which automatically adapt. For custom colors, create asset catalog variants for Any Appearance and Dark Appearance.
What navigation pattern should I use?
Use TabView for 3-5 main sections, NavigationStack for drill-down hierarchies, and .sheet for focused tasks. Never use hamburger/drawer menus on iOS.
How do I ensure my app works with VoiceOver?
Add accessibilityLabel to all interactive elements, use accessibilityHint for complex actions, set accessibilityTrait appropriately, and test with VoiceOver enabled regularly.