agentleFS
Sign inStart free
mejbaurbaharmejbaurbahar/software-tester-skills/skills/localization-testing/SKILL.md

localization-testing

Skill1 starsChanged 52 days agoMITView on GitHub

Use when verifying internationalization (i18n) and localization (l10n) — string truncation, pseudo-localization, Right-to-Left (RTL) layout rendering, date/time/currency formatting, and UTF-8 encoding.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify buttons, cards, table columns, and navigation bars do not clip or wrap awkwardly.

    line 19
  2. Distinctive:

    Test RTL languages (Arabic, Hebrew, Persian, Urdu).

    line 21
  3. Distinctive:

    Verify UTF-8 end-to-end (database, API headers, frontend rendering).

    line 25
  4. Distinctive:

    Test with non-Latin scripts (Chinese, Japanese, Korean, Cyrillic, Greek), accented characters (é, ü, ñ, ø), and emojis.

    line 26
  5. Distinctive:

    Timezones: Verify correct calculation across daylight saving transitions and UTC conversions.

    line 30
  6. Distinctive:

    Use pseudo-localization tools to replace English characters with accented versions and expand length:

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Localization (l10n) & Internationalization (i18n) Testing

Overview

Localization (l10n) testing ensures that software adapts seamlessly to different languages, cultures, and geographic regions without functional breakage, visual truncation, or data corruption.

Core Verification Areas

  1. Visual Layout & Text Expansion:
    • Translations frequently expand by 30% to 50% compared to English (e.g. German, French, Finnish).
    • Verify buttons, cards, table columns, and navigation bars do not clip or wrap awkwardly.
  2. Bidirectional & Right-to-Left (RTL) Support:
    • Test RTL languages (Arabic, Hebrew, Persian, Urdu).
    • Layouts must flip horizontally (dir="rtl"): navigation, icons with directionality, chevrons, and alignment.
    • Text with mixed LTR/RTL (e.g. English brand name in an Arabic sentence) must render in correct reading order.
  3. Character Encoding & Multi-Byte Support:
    • Verify UTF-8 end-to-end (database, API headers, frontend rendering).
    • Test with non-Latin scripts (Chinese, Japanese, Korean, Cyrillic, Greek), accented characters (é, ü, ñ, ø), and emojis.
  4. Locale-Specific Formatting:
    • Dates: MM/DD/YYYY (US) vs DD/MM/YYYY (UK/EU) vs YYYY-MM-DD (ISO/Asia).
    • Numbers & Currencies: $1,234.56 (US) vs 1.234,56 € (DE/FR).
    • Timezones: Verify correct calculation across daylight saving transitions and UTC conversions.
  5. Pseudo-Localization (Pseudo-loc):
    • Use pseudo-localization tools to replace English characters with accented versions and expand length:
      • Example: [!!! Ṗřǿḓŭƈťş !!!]
    • Instantly exposes hardcoded strings (untranslated) and layout truncation before translations arrive.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free