⚡AgentSkills
🌐 Localization & i18n · Linguistic Quality

Get locale data right: dates, numbers, names

ICU-driven formatting, name ordering, address forms, and timezone correctness per locale.

foundation~25 minLocalization Engineersi18n DevelopersLocalization Managers

Steps

  1. 1Format dates/numbers/currency through Intl APIs — never hand-roll patterns
  2. 2Collect names as given/family separately OR single full-name field, per culture
  3. 3Address forms per country via validated libraries, not one global template
  4. 4Store timestamps UTC + IANA zone; display in user zone explicitly
  5. 5Pluralization via CLDR rules for every supported language in tests
  6. 6Locale smoke suite: de long text, ar RTL, ja no-spaces, es-MX currency

Common Pitfalls

  • ▲MM/DD/YYYY assumptions shipped worldwide
  • ▲Currency symbols concatenated in wrong position per locale

Commands

Install with skills CLI
$ npx skills add aniruddhaadak80/skills --skill locale-data-correctness
Install globally
$ npx skills add aniruddhaadak80/skills --skill locale-data-correctness -g

Tags

#icu#formats#global-ready#localization-i18n#linguistic-quality

Related skills

Run linguistic QA that catches real errorsintermediate

In-context review, error typology scoring, and vendor feedback loops improving over releases.

🌐 Localization & i18n·~35m
Open →