localization-developer
A context-aware router for the Anytype iOS localization system, enforcing strict rules for string management.
Install
mkdir -p .claude/skills/localization-developer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4308" && unzip -o skill.zip -d .claude/skills/localization-developer && rm skill.zipInstalls to .claude/skills/localization-developer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Context-aware routing to the Anytype iOS localization system. Use when working with .xcstrings files, Loc constants, hardcoded strings, or user-facing text.Key capabilities
- →Search for existing localization keys in generated Swift files
- →Add new localization keys to specific .xcstrings files
- →Generate Swift code from .xcstrings files
- →Use generated `Loc` constants for UI text
- →Remove unused localization keys from source .xcstrings files
- →Handle dynamic localization with parameters using generated functions
How it works
The skill guides the user to search for existing keys, add new keys to the correct .xcstrings file, and then run a generation script to update the `Strings.swift` file for use in UI.
Inputs & outputs
When to use localization-developer
- →Updating UI strings
- →Managing localization keys
- →Maintaining Anytype iOS translation files
About this skill
Localization Developer (Smart Router)
Purpose
Context-aware routing to the Anytype iOS localization system. Helps you navigate the 3-file .xcstrings structure and use Loc constants correctly.
When Auto-Activated
- Working with
.xcstringsfiles - Using
Locconstants - Discussing hardcoded strings or user-facing text
- Keywords: localization, strings, text, Loc., .xcstrings
🚨 CRITICAL RULES (NEVER VIOLATE)
- NEVER use hardcoded strings in UI - Always use
Locconstants - NEVER create duplicate keys across the 3 .xcstrings files - Breaks code generation
- NEVER edit non-English translations - Only update English (
en), Crowdin handles others - ALWAYS search for existing keys first - Reuse before creating new
- ALWAYS run
make generateafter editing .xcstrings files
📋 Quick Workflow
- Search existing:
rg "yourSearchTerm" Modules/Loc/Sources/Loc/Generated/Strings.swift - If found: Reuse existing key
- If not found: Add to appropriate .xcstrings file (see decision tree below)
- Generate:
make generate - Use:
AnytypeText(Loc.yourKey, style: .uxCalloutMedium)
🗂️ The 3-File System
Decision Tree
Is this text for authentication/login/vault?
YES → Auth.xcstrings (86 keys)
NO → Continue
Is this text for spaces/objects/collaboration?
YES → Workspace.xcstrings (493 keys)
NO → Continue
Is this text for settings/widgets/general UI?
YES → UI.xcstrings (667 keys)
File Locations
- Auth.xcstrings:
Modules/Loc/Sources/Loc/Resources/Auth.xcstrings - Workspace.xcstrings:
Modules/Loc/Sources/Loc/Resources/Workspace.xcstrings - UI.xcstrings:
Modules/Loc/Sources/Loc/Resources/UI.xcstrings
Generated output: All 3 files → single Strings.swift (~5,000 lines, 1,246 total keys)
🎯 Adding Keys
Format (add to appropriate .xcstrings file)
"Your localization key" : {
"extractionState" : "manual",
"localizations" : {
"en" : {
"stringUnit" : {
"state" : "translated",
"value" : "Your English text here"
}
}
}
}
Key naming:
- Short keys:
"No properties yet"✅ - Not full sentences:
"No properties yet. Add some."❌ - Hierarchical:
"QR.join.title"→Loc.Qr.Join.title
🔢 Dynamic Localization (Parameters)
✅ CORRECT - Use generated functions
// String: "You've reached the limit of %lld editors"
Loc.SpaceLimit.Editors.title(4)
// String: "Welcome, %@!"
Loc.welcomeMessage("John")
❌ WRONG - Never use String(format:)
String(format: Loc.limitReached, 10) // DON'T DO THIS
Why: SwiftGen auto-generates parameterized functions for format specifiers (%lld, %d, %@).
Format specifiers:
%lld→ Int parameter%d→ Int parameter%@→ String parameter%.1f→ Double parameter
🗑️ Removing Unused Keys
- Search:
rg "keyName" --type swift - If only in Strings.swift: Key is orphaned
- Remove from source .xcstrings file
- Generate:
make generate
⚠️ Common Mistakes
Hardcoded Strings
// ❌ WRONG
Text("Delete")
// ✅ CORRECT
Text(Loc.delete)
Duplicate Keys Across Files
// In Auth.xcstrings
"Settings" : { ... }
// In UI.xcstrings
"Settings" : { ... } // ❌ DUPLICATE! Breaks generation
Using String(format:)
// ❌ WRONG
String(format: Loc.limitReached, 10)
// ✅ CORRECT
Loc.limitReached(10)
Editing Non-English
// ❌ WRONG - Crowdin will overwrite
"de" : { "value" : "Meine Übersetzung" }
// ✅ CORRECT - Only edit English
"en" : { "value" : "My translation" }
📚 Complete Documentation
Full Guide: Anytype/Sources/PresentationLayer/Common/LOCALIZATION_GUIDE.md
For comprehensive coverage of:
- Detailed 3-file system explanation
- Key naming patterns and conventions
- Dynamic localization with all format specifiers
- Translation workflow with Crowdin
- Removing orphaned keys
- Generated file structure
- Complete examples and troubleshooting
✅ Workflow Checklist
- Searched for existing keys (
rgin Strings.swift) - Added to correct .xcstrings file (Auth/Workspace/UI)
- No duplicate keys across files
- Only updated English (
en) - Ran
make generate - Used generated key:
Loc.yourKey - No hardcoded strings in UI
🔗 Related Skills & Docs
- ios-dev-guidelines →
IOS_DEVELOPMENT_GUIDE.md- Never use hardcoded strings - code-generation-developer →
CODE_GENERATION_GUIDE.md- Understanding make generate - design-system-developer → Using Loc constants in UI components
Navigation: This is a smart router. For deep details, always refer to LOCALIZATION_GUIDE.md.
When not to use it
- →When editing non-English translations
- →When creating duplicate keys across .xcstrings files
- →When using hardcoded strings in UI
Limitations
- →Only English (`en`) translations should be updated directly
- →Duplicate keys across the 3 .xcstrings files are not allowed
- →Hardcoded strings in UI are prohibited
How it compares
This skill enforces a structured 3-file .xcstrings system and automates Swift code generation for localization, preventing common errors like hardcoded strings or duplicate keys.
Compared to similar skills
localization-developer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| localization-developer (this skill) | 1 | 6mo | No flags | Intermediate |
| i18n-expert | 2 | 6mo | Review | Intermediate |
| React + Ant Design Frontend | 0 | 5mo | Review | Intermediate |
| dotnet-localization | 0 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by anyproto
View all by anyproto →You might also like
i18n-expert
daymade
This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages, and validating key parity, pluralization, and formatting.
React + Ant Design Frontend
daithang-organization
Complete guide for the SE104_VLEAGUE React frontend — pages, services, components, auth flow, i18n, and patterns
dotnet-localization
rudironsoni
>-
localization
Develop4Us-Company
Instructions for managing localization and resource files in the AppProject .NET template. Covers adding translation keys to .resx files, resource key naming conventions, placeholder formatting, and maintaining consistency across en-US, pt-BR, and es-ES translations. Use when the user needs to add o
translations
mikopbx
Управление многоязычными переводами на 29 языков с приоритетом русского языка. Использовать при добавлении новых переводов, переводе на все языки, проверке консистентности или удалении устаревших ключей.
skills
jralvarenga
Package map and reading order for Better Translate product skills.