Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dpearson2699/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.
Passed 20 of 22 test cases with the skill, and 17 of 22 without it.
and 3 more in the full report
3 fixed17 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am building an iOS app where localizations inside a Swift package target aren't showing up in translated languages. Please analyze my target setup and provide a step-by-step diagnostic checklist and code solution to ensure translated strings resolve correctly.
| Checked | Without skill | With skill |
|---|---|---|
| The checklist verifies that Package.swift declares defaultLocalization. | Passed | Passed |
| The checklist verifies that the target resources list processes the catalog path. | Missed | Passed |
| The checklist verifies that Localizable.xcstrings is located within the processed target resource path. | Missed | Passed |
| The response places package manifest verification steps prior to recommending bundle debugging with bundle: .module. | Passed | Passed |
| The response refrains from recommending NSLocalizedString for new Swift code. | Missed | Passed |
The instructions your model reads when the skill loads.
Localize Apple-platform apps with String Catalogs, modern string types, locale-aware formatting, and right-to-left layout.
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:
// SwiftUI -- automatically extracted (LocalizedStringKey)
Text("Welcome back") // key: "Welcome back"
Label("Settings", systemImage: "gear")
Button("Save") { }
Toggle("Dark Mode", isOn: $dark)
// Programmatic -- automatically extracted
String(localized: "No items found")
LocalizedStringResource("Order placed")
// Plain String: not extracted or localized
let msg = "Hello"
test cases passed, vs 17 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.