Agent skill
iOS Localization & Assets
Standards for String Catalogs, L10n, and Asset Management.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/localization
Metadata
Additional technical details for this skill
- labels
-
ios localization l10n assets xcassets
- triggers
-
{ "files": [ "**/*.stringcatalog", "**/*.xcassets", "**/*.strings" ], "keywords": [ "LocalizedStringResource", "NSLocalizedString", "String(localized:)" ] }
SKILL.md
iOS Localization & Assets Standards
Priority: P1
Implementation Guidelines
Localization (L10n)
- String Catalogs (.stringcatalog): Use for primary localization in Xcode 15+. It provides a visual editor and compile-time checks for missing translations.
- Native Implementation: Use
String(localized: "key")orLocalizedStringResource. Avoid manualNSLocalizedStringwhere possible. - Pluralization: Use String Catalogs' built-in pluralization support instead of complex code logic.
- Formatting: Use
FormattedAPI for dates, numbers, and currencies to respect the user's locale.
Asset Management
- Asset Catalogs (.xcassets): Keep assets organized. Use folders with "Provides Namespace" enabled for large projects.
- SF Symbols: Use for standard icons to ensure consistency and accessibility.
- Vector Assets: Use PDF or SVG and enable "Preserve Vector Data" for resolution independence.
Best Practices
- Hardcoded Strings: Never use hardcoded strings in UI. Every user-facing string must be localized.
- Base Bundle: Ensure
Baselocalization is complete before adding other languages.
Anti-Patterns
- Manual String Formatting:
**No manual currency symbol concat**: Use NumberFormatter or .formatted(.currency). - Loose Asset Files:
**No loose png/jpg files in repo**: Always use Asset Catalogs. - Untranslated Keys:
**No placeholder strings**: Ensure 100% coverage in String Catalogs.
References
- L10n & Asset Organization
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?