← ClaudeAtlas

ios-localizationlisted

Production-grade iOS localization skill covering String Catalogs (.xcstrings), CLDR pluralization, SwiftUI/UIKit localization APIs, RTL layout, date/number/currency formatting, and enterprise patterns (modular apps, white-label, accessibility localization). This skill should be used when creating or editing localized iOS strings, working with .xcstrings or .strings files, implementing pluralization, formatting dates/numbers/currencies for display, building RTL-compatible layouts, localizing accessibility labels, setting up localization in Swift Packages, or reviewing code for localization correctness. Use this skill any time someone is working with iOS localization, i18n, l10n, String Catalogs, plural rules, RTL, date formatting, or translated strings — even if they only say 'add a string' or 'format this date' or 'make this work in Arabic.' Also audit any newly generated user-facing iOS code for localization failures before finalizing — AI coding assistants systematically produce broken localization (hardcod
christim427-rgb/ios-agent-skills · ★ 1 · AI & Automation · score 77
Install: claude install-skill christim427-rgb/ios-agent-skills
# iOS Localization Production-grade localization skill for iOS codebases. AI coding assistants systematically produce broken localization code across 30+ identifiable patterns — from missing Slavic plural categories to hardcoded left/right constraints that shatter RTL layouts. This skill intercepts those patterns and enforces correct localization from the start. Covers String Catalogs (.xcstrings), CLDR pluralization, SwiftUI/UIKit APIs, date/number/currency formatting, RTL layout, accessibility localization, and enterprise patterns (modular apps, white-label, Swift Packages). ## Why This Skill Exists AI assistants generate localization code trained predominantly on English-only codebases. The result: only `one`/`other` plurals (breaking Russian, Ukrainian, Polish, Arabic), hardcoded English strings, `String(format:)` without positional specifiers, `dateFormat` strings that break in non-Gregorian calendars, and left/right constraints that break for 400M+ Arabic/Hebrew users. These bugs are silent in English testing and only surface in production. ## Quick Decision Trees ### Which localization API to use? ``` Is the project SwiftUI or UIKit? ├── SwiftUI → String literals in Text/Button/Toggle auto-localize │ ├── Need to prevent localization? → Text(verbatim: "v2.0") │ ├── Dynamic key from variable? → Text(LocalizedStringKey(key)) │ ├── In a Swift Package? → Text("key", bundle: .module) │ └── Passing localized content across APIs? → Use LocalizedStringResource └─