Skill

i18n

From hb

Audits internationalization coverage by detecting i18n libraries, finding hardcoded user-facing strings in frontend code, and comparing locale files for missing translations.

npx claudepluginhub helderberto/agent-skills --plugin hb

Popularity

Stars

Forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/hb:i18n

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Read `package.json` for i18n library:

Supporting Files

references/patterns.md

SKILL.md

56 lines · ~490 tokens

Similar Skills

Harness i18n

Detects hardcoded strings, missing translations, locale-sensitive formatting, RTL issues, and concatenation anti-patterns across web, mobile, and backend codebases.

1 file

harness-claude

i18n

Audits and implements internationalization: extracts hardcoded strings, sets up react-i18next/vue-i18n/next-intl, handles ICU pluralization, Intl date/number/currency formatting, RTL logical CSS properties.

godmode

i18n-localization

37.9k

Guides i18n/l10n implementation: detects hardcoded strings, manages translations/locale files, RTL support. Patterns for React, Next.js, Python.

1 file

antigravity-awesome-skills

Stats

LanguagePython

Stars10

Forks1

MaintenanceExcellent

Last CommitJun 8, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

i18n Audit

Detection

Read package.json for i18n library:

react-i18next / i18next

next-intl

vue-i18n

react-intl (FormatJS)

Read locale files to understand key structure (e.g. src/locales/en.json).

Workflow

Detect i18n library and locale file locations

Search JSX/TSX/Vue files for hardcoded user-facing strings (see patterns.md):

String literals in JSX: <p>Hello world</p>
String props: placeholder="Search...", label="Submit"
aria-label="Close menu"

Compare locale files — find missing keys between locales:

# keys in en.json but missing in pt.json

Report findings

Output format

Hardcoded strings (file:line):

src/components/Header.tsx:12 "Welcome back" → suggest key: header.welcomeBack src/components/Form.tsx:34 placeholder="Search..." → suggest key: form.searchPlaceholder

Missing translations (key present in base locale but absent in others):

Key: dashboard.emptyState missing in: pt-BR, es Key: errors.networkTimeout missing in: pt-BR

Rules

Only flag user-visible strings (skip internal IDs, CSS classes, URLs, enum values)

Suggest translation key names in camelCase matching project convention

Never auto-modify locale files — report only

Error Handling

If no i18n library detected → report project may not use i18n; still list any hardcoded strings found

If no locale files found → skip missing-key comparison; only report hardcoded strings

If locale files are not JSON (e.g. .po, .yaml) → read them anyway and adapt key comparison logic

i18n Audit

Detection

Read package.json for i18n library:

react-i18next / i18next
next-intl
vue-i18n
react-intl (FormatJS)

Read locale files to understand key structure (e.g. src/locales/en.json).

Workflow

Detect i18n library and locale file locations
Search JSX/TSX/Vue files for hardcoded user-facing strings (see patterns.md):
- String literals in JSX: <p>Hello world</p>
- String props: placeholder="Search...", label="Submit"
- aria-label="Close menu"
Compare locale files — find missing keys between locales:
```
# keys in en.json but missing in pt.json
```
Report findings

Output format

Hardcoded strings (file:line):

src/components/Header.tsx:12  "Welcome back"  → suggest key: header.welcomeBack
src/components/Form.tsx:34    placeholder="Search..."  → suggest key: form.searchPlaceholder

Missing translations (key present in base locale but absent in others):

Key: dashboard.emptyState  missing in: pt-BR, es
Key: errors.networkTimeout  missing in: pt-BR

Rules

Only flag user-visible strings (skip internal IDs, CSS classes, URLs, enum values)
Suggest translation key names in camelCase matching project convention
Never auto-modify locale files — report only

Error Handling

If no i18n library detected → report project may not use i18n; still list any hardcoded strings found
If no locale files found → skip missing-key comparison; only report hardcoded strings
If locale files are not JSON (e.g. .po, .yaml) → read them anyway and adapt key comparison logic

i18n

Popularity

Invocation

Context Preview

Supporting Files

SKILL.md

Similar Skills

Help us improve

Help us improve

Find plugins for your project

i18n

Popularity

Invocation

Context Preview

Supporting Files

SKILL.md

i18n Audit

Detection

Workflow

Output format

Rules

Error Handling

Similar Skills

Help us improve

i18n Audit

Detection

Workflow

Output format

Rules

Error Handling