Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rshankras/localization-setup
Generate internationalization (i18n) infrastructure for multi-language support in iOS/macOS apps.
Passed 15 of 22 test cases with the skill, and 14 of 22 without it.
2 fixed13 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
What directory structure should be created when organizing generated localization code and catalog resources in a Swift iOS project?
| Checked | Without skill | With skill |
|---|---|---|
| Places the String Catalog file in a Resources directory. | Passed | Passed |
| Places supporting Swift localization code inside Sources/Localization/. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate internationalization (i18n) infrastructure for multi-language support in iOS/macOS apps.
Before generating, verify:
Existing Localization
# Check for existing localization files
find . -name "*.xcstrings" -o -name "Localizable.strings" 2>/dev/null | head -5
find . -name "*.lproj" -type d 2>/dev/null | head -5
Deployment Target
# String Catalogs require iOS 16+ / macOS 13+
grep -r "IPHONEOS_DEPLOYMENT_TARGET\|MACOSX_DEPLOYMENT_TARGET" *.xcodeproj 2>/dev/null
Project Structure
# Find project for adding localization
find . -name "*.xcodeproj" | head -1
test cases passed, vs 14 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.