ios-localization
Implement, review, or improve localization and internationalization in iOS/macOS apps — String Catalogs (.xcstrings), generated localizable symbols, stable key naming, LocalizedStringKey, LocalizedStringResource, pluralization, FormatStyle for numbers/dates/measurements, right-to-left layout, Dynamic Type, and locale-aware formatting. Use when adding multi-language support, setting up String Catalogs, enabling generated symbols for compile-time-safe localization keys, handling plural forms, formatting dates/numbers/currencies for different locales, testing localizations, or making UI work corr
Profile →npx skills add dpearson2699/swift-ios-skills --skill ios-localization --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# iOS Localization & Internationalization Localize Apple-platform apps with String Catalogs, modern string types, locale-aware formatting, and right-to-left layout. ## Contents - [String Catalogs and Generated Symbols](#string-catalogs-and-generated-symbols) - [String Types -- Decision Guide](#string-types-decision-guide) - [String Interpolation in Localized Strings](#string-interpolation-in-localized-strings) - [Pluralization](#pluralization) - [FormatStyle -- Locale-Aware Formatting](#formatstyle-locale-aware-formatting) - [Right-to-Left (RTL) Layout](#right-to-left-rtl-layout) - [Common Mistakes](#common-mistakes) - [Localization Review Checklist](#review-checklist) - [References](#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: ```swift // Swi
- Contents
- String Catalogs and Generated Symbols
- String Types -- Decision Guide
- LocalizedStringKey (SwiftUI default)
- String(localized:) -- Modern NSLocalizedString replacement
- LocalizedStringResource -- Pass localization info without resolving
- String Interpolation in Localized Strings
- Pluralization
- Setup in String Catalog
- Device Variations
- FormatStyle -- Locale-Aware Formatting
- Dates
- Numbers
- Measurements
What does the ios-localization skill do?
Implement, review, or improve localization and internationalization in iOS/macOS apps — String Catalogs (.xcstrings), generated localizable symbols, stable key naming, LocalizedStringKey, LocalizedStringResource, pluralization, FormatStyle for numbers/dates/measurements, right-to-left layout, Dynamic Type, and locale-aware formatting. Use when adding multi-language support, setting up String Catalogs, enabling generated symbols for compile-time-safe localization keys, handling plural forms, formatting dates/numbers/currencies for different locales, testing localizations, or making UI work corr
How do I install it?
Run `npx skills add dpearson2699/swift-ios-skills --skill ios-localization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dpearson2699/swift-ios-skills, a repository with 963 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.