⚡AgentSkills
🌐 Localization & i18n · String Engineering

Externalize strings without breaking the app

Systematic extraction, key naming, and context comments making translation safe.

foundation~30 minLocalization Engineersi18n DevelopersLocalization Managers

Steps

  1. 1Extract all user-visible strings; ban literals in components via lint rule
  2. 2Name keys by semantic meaning (checkout.payment.decline), never by English text
  3. 3Attach translator context comments: where shown, character limits, tone
  4. 4Handle interpolation with ICU MessageFormat; never concatenate translated fragments
  5. 5Add pseudo-localization build mode surfacing hardcoded strings visually
  6. 6Test longest locale (usually de) for layout breakage before shipping

Common Pitfalls

  • ▲Concatenated sentences untranslatable in any other grammar
  • ▲Keys named after current English copy, shattering on rewording

Commands

Install with skills CLI
$ npx skills add aniruddhaadak80/skills --skill string-engineering-externalize-strings-audit
Install globally
$ npx skills add aniruddhaadak80/skills --skill string-engineering-externalize-strings-audit -g

Tags

#i18n#strings#refactoring#localization-i18n#string-engineering

Related skills

Support RTL layouts properlyintermediate

Logical properties, mirrored iconography decisions, and bidi text handling done right.

🌐 Localization & i18n·~35m
Open →