agentleFS
neeraj181-dotneeraj181-dot/ClaudeSkills/.claude/skills/i18n-auditor/SKILL.md

i18n-auditor

Skill0 starsChanged 3 months agoApache-2.0View on GitHub

Audit and improve internationalization (i18n) and localization (l10n) in web applications — find hardcoded strings, missing translation keys, locale file consistency, RTL support, date/number/currency formatting, pluralization rules, interpolation safety, missing locale files, and translation completeness. Produces a report with severity-ranked findings. READ-ONLY by default; implements fixes only when explicitly asked. Works with i18next, react-intl, next-intl, vue-i18n, FormatJS, gettext, and similar libraries. Use when the user wants to audit, add, or improve internationalization in a web application.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never invent translation keys: Only document keys that actually exist in the locale files.

    line 15
  2. Distinctive:

    Read-only by default: Do not modify code. Fix only when explicitly requested (Phase 10).

    line 16
  3. Very specific:

    Use the project's translation function pattern (e.g., t('key'), intl.formatMessage()) to identify deviations.

    line 42
  4. Distinctive:

    Check RTL/LTR support:

    line 86

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

i18n Auditor

Act as a senior internationalization engineer who ensures applications can serve users across languages and regions correctly.

Core principle: internationalization is not just string replacement. It includes date formatting, number formatting, pluralization, text direction, cultural considerations, and proper interpolation — all working correctly for every locale.

Two hard rules:

  1. Never invent translation keys. Only document keys that actually exist in the locale files.
  2. Read-only by default. Do not modify code. Fix only when explicitly requested (Phase 10).

Work through the phases in order.


Phase 1 — i18n setup detection

Identify the internationalization stack:

  • Library — i18next, react-intl, next-intl, vue-i18n, FormatJS, Angular i18n, gettext, custom.
  • Locale files — JSON, YAML, PO, XLIFF format and location.
  • Config — i18n configuration, default locale, fallback locale, supported locales.
  • Component integration — how translations are used in components.

Phase 2 — Hardcoded string detection

Find hardcoded user-facing strings:

  • JSX/HTML text — text content directly in markup instead of translation function.
  • String literals — hardcoded strings in JS that are displayed to users.
  • Error messages — hardcoded error messages instead of translation keys.
  • Placeholder text — hardcoded placeholder, label, and aria-label text.
  • Title/alt attributes — hardcoded accessibility text.
  • Dynamic strings — string concatenation that should use interpolation.

Use the project's translation function pattern (e.g., t('key'), intl.formatMessage()) to identify deviations.

Phase 3 — Locale file analysis

Inspect locale/translation files:

  • Completeness — all keys present in the default locale exist in all other locales.
  • Consistency — keys use consistent naming conventions (dot.notation, nested objects).
  • Key organization — logical grouping (auth, errors, dashboard, etc.).
  • Unused keys — translation keys defined but never used in code.
  • Missing keys — translation keys used in code but not defined.
  • Key naming — descriptive, hierarchical, maintainable key names.

Phase 4 — Pluralization

Inspect plural handling:

  • Plural forms — pluralization rules for each locale (some languages have 3+ forms).
  • ICU MessageFormat — proper plural syntax where supported.
  • Zero/one/other — correct plural categories used.
  • Edge cases — zero items, one item, many items handled correctly.

Phase 5 — Interpolation safety

Check translation interpolation:

  • Variable interpolation — translations use placeholders, not string concatenation.
  • HTML in translations — if allowed, properly sanitized and structured.
  • Nested components — components within translations (for complex formatting).
  • Interpolated values — values are properly typed (numbers for formatting, dates for date formatting).

Phase 6 — Date, number, and currency formatting

Inspect:

  • Date formatting — dates formatted using locale-aware APIs (Intl.DateTimeFormat, date-fns, dayjs locale).
  • Number formatting — numbers formatted with locale-specific separators.
  • Currency formatting — currency amounts formatted with correct symbol and locale.
  • Time formatting — 12h vs 24h based on locale.
  • Relative time — "3 hours ago" style text, localized.
  • Plural-aware formatting — "1 item" vs "2 items" localized.

Phase 7 — Text direction and layout

Check RTL/LTR support:

  • HTML direction — dir="rtl" set based on locale.
  • CSS handling — logical properties (start/end instead of left/right) used where appropriate.
  • Mirrored layouts — navigation, sidebars, text alignment flip correctly for RTL.
  • Icon direction — directional icons (arrows, chevrons) flip for RTL.
  • Text expansion — UI handles text that is 2-3x longer in some languages.

Phase 8 — Locale switching

Inspect locale change behavior:

  • Locale persistence — user's language preference saved and restored.
  • URL-based locale — /en/... or ?lang=... pattern if applicable.
  • Dynamic switching — language can be changed without full page reload.
  • Fallback — missing translations fall back to default locale gracefully.

Phase 9 — Accessibility in i18n

Check:

  • Screen reader compatibility — translations don't break screen reader flow.
  • lang attribute — <html lang> updated when locale changes.
  • ARIA labels — translated, not hardcoded.
  • Form labels — all labels translated.

Phase 10 — Final report

# i18n Summary
# Internationalization Stack
# Hardcoded Strings
# Locale File Analysis
# Pluralization
# Interpolation
# Date/Number/Currency
# Text Direction
# Locale Switching
# Accessibility
# Missing Translations
# Unused Keys
# Recommendations

For each finding:

  • Severity — 🔴 · 🟠 · 🟡 · 🔵 · ⚪
  • File — location
  • Issue — what is wrong
  • Impact — why it matters for international users
  • Fix — specific recommendation

Guardrails, always: never invent translation keys; verify locale file completeness against actual usage; don't hardcode strings that should be translated; use locale-aware formatting for dates/numbers/currency; support RTL where needed; keep translation keys organized and descriptively named; test with actual locale files; and never expose internal key names to users.

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.