I18n
My personal SDLC toolbelt for AI coding agents — PRD to ship.
npx -y skills add helderberto/agent-skills --skill i18nAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Audit internationalization coverage and find hardcoded strings. Use when user asks to "check i18n", "/i18n", "find hardcoded strings", "check translations", or wants to verify translation coverage. Don't use for backend string extraction, non-frontend code, or projects without an i18n library.
SKILL.md
1.9 KB, as published. Nobody here has run it
i18n Audit
Detection
Read package.json for i18n library:
react-i18next/i18nextnext-intlvue-i18nreact-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"
- String literals in JSX:
- Compare locale files — find missing keys between locales
- 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