How do I install the Localize Strings skill?

Run npx skillmds@latest add rokartur/localize-strings in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Localize Strings skill do?

Keep Localizable.xcstrings in lockstep with the code. Use whenever code adds, edits, or removes any user-facing string, or when LocalizationCatalogTests fails. It is listed under Coding & Dev Tools on SkillMD.

Is Localize Strings safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Localize Strings?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Localize Strings free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Localize Strings?

rokartur (@rokartur) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Localize Strings by rokartur — Agent Skill

Name: Localize Strings
Author: rokartur

File contents

Localize strings

Every user-facing string ships translated in five locales. The catalog is version-controlled JSON and LocalizationCatalogTests pins full coverage — an English-only key fails the suite, it does not silently ship.

1. Use the localized form in code

User-facing text is String(localized: "…"); enum display names localize too. A bare literal in UI code ships untranslated — wrap it.

2. Add the catalog entries

Edit BetterCmdTab/Localizable.xcstrings directly (it is JSON). For each new key add translations for all of: de, es, fr, pl, zh-Hans. Copy the exact JSON shape of a neighboring entry, keep keys sorted where the surrounding file is sorted, and keep format specifiers (%@, %d, …) identical across every locale — specifier drift is a test failure. Remove catalog entries whose code key was deleted.

3. Verify

xcodebuild -scheme "BetterCmdTab Debug" -destination 'platform=macOS' test \
  -only-testing:BetterCmdTabTests/LocalizationCatalogTests

Complete when: the suite passes with the new keys present in all five locales.

Frequently asked questions

Localize Strings