Ios Localization

Handles the full iOS localization stack: String Catalogs, generated symbols for type-safe keys, LocalizedStringResource for App Intents and widgets, FormatStyle for locale-aware numbers and dates, and RTL layout testing. The guide breaks down when to use LocalizedStringKey versus String(localized:) versus LocalizedStringResource, which trips up a lot of people new to modern iOS localization. Covers Xcode 26's generated symbols feature that lets you write `.roomAvailable` instead of stringly-typed keys. If you're shipping an app in multiple languages or need to pass App Store review in non-English markets, this walks through the mechanics and common mistakes that cause rejections or broken Arabic/Hebrew layouts.

skills.sh installs: 4.5K
GitHub stars: 1.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add dpearson2699/swift-ios-skills --skill ios-localization --agent claude-code

Installs into .claude/skills of the current project.

Files

iOS Localization & Internationalization

Localize Apple-platform apps with String Catalogs, modern string types, locale-aware formatting, and right-to-left layout.

String Catalogs and Generated Symbols
String Types -- Decision Guide
String Interpolation in Localized Strings
Pluralization
FormatStyle -- Locale-Aware Formatting
Right-to-Left (RTL) Layout
Common Mistakes
Localization Review Checklist
References

String Catalogs and Generated Symbols

String Catalogs are the recommended Xcode 15+ workflow for new localization work. They keep localizable strings, pluralization rules, and device variations together in an Xcode-managed JSON file with a visual editor. Legacy .strings and .stringsdict files can coexist during migration, but new Swift and SwiftUI code should default to String Catalogs.

How automatic extraction works:

Xcode scans for these patterns on each build:

SKILL.md on GitHub