i18n-frontend-implementer — Claude Code skill
This skill adds frontend i18n setup with translation files, locale-aware formatting, plural handling, and language switching.
npx skills add patricio0312rev/skills --skill i18n-frontend-implementer -a claude-codeWhat i18n-frontend-implementer does
i18n-frontend-implementer guides an internationalization setup with next-intl, react-i18next, or a similar library. It covers locale dictionaries such as locales/en.json and locales/es.json, provider wiring, and hierarchical translation namespaces.
The skill also handles date, number, and currency formatting, plural rules, and a language switcher. Its guidance includes moving interface text into translations, supporting RTL languages, and loading translations lazily. Choose the i18n library before applying the setup, since the implementation follows the project’s selected stack.
What it helps with
- add translations to a frontend app
- organize keys into translation namespaces
- format dates, numbers, and currency by locale
- handle pluralized messages
- build a language switcher
Example prompts for the agent
- Set up i18n in this frontend with
next-intl, then createlocales/en.jsonandlocales/es.json. - Organize the translation keys, add locale-aware date and currency formatting, and wire in language switching.
- Review plural messages and add RTL language support to the current interface.
How to install i18n-frontend-implementer
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill i18n-frontend-implementer -a claude-code2Manually: put the files in place
~/.claude/skills/i18n-frontend-implementer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/i18n-frontend-implementer/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill i18n-frontend-implementer -a codex2Manually: put the files in place
.agents/skills/i18n-frontend-implementer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill i18n-frontend-implementer -a cursor2Manually: put the files in place
.cursor/skills/i18n-frontend-implementer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install patricio0312rev/skills i18n-frontend-implementer2Manually: put the files in place
.github/skills/i18n-frontend-implementer/SKILL.md1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill i18n-frontend-implementer -a gemini-cli2Platform CLI
gemini skills install https://github.com/patricio0312rev/skills --path frontend/i18n-frontend-implementerManually: put the files in place
.devin/skills/i18n-frontend-implementer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill i18n-frontend-implementer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about i18n-frontend-implementer
How do I install i18n-frontend-implementer in Claude Code?
Run npx skills add patricio0312rev/skills --skill i18n-frontend-implementer -a claude-code, then check ~/.claude/skills/i18n-frontend-implementer/SKILL.md.
What does i18n-frontend-implementer do?
It helps add frontend translations, locale-aware formatting for dates, numbers, and currency, plural rules, and language switching.
Which libraries does the skill support?
The instructions use next-intl, react-i18next, or a comparable internationalization library.
Source text
SKILL.md · MIT
---
name: i18n-frontend-implementer
description: Adds internationalization (i18n) infrastructure with translation plumbing, scalable key strategy, formatters for dates/numbers/currency, plural rules, and language switching. Use when implementing "internationalization", "translations", "multi-language support", or "i18n".
---
# i18n Frontend Implementer
Implement internationalization with next-intl, react-i18next, or similar libraries.
## Core Setup
**1. Install**: `npm install next-intl` or `react-i18next`
**2. Create dictionaries**: `locales/en.json`, `locales/es.json`
**3. Provider setup**: Wrap app with IntlProvider
**4. Translation keys**: Hierarchical namespace structure
**5. Formatters**: Date, number, currency formatting
**6. Language switcher**: Dropdown or flags UI
## Translation Structure
```json
{
"common": { "nav": { "home": "Home", "about": "About" } },
"auth": { "login": "Sign In", "logout": "Sign Out" },
"errors": { "required": "{field} is required" }
}
```
## Usage Examples
```tsx
const t = useTranslations('common');
<h1>{t('nav.home')}</h1>
// With plurals
t('items', { count: 5 }) // "5 items"
// With formatting
<p>{formatDate(date, { dateStyle: 'long' })}</p>
```
## Best Practices
Use namespaces for organization, extract all text to translations, handle plurals properly, format dates/numbers per locale, provide language switcher, support RTL languages, lazy-load translations.
© patricio0312rev · MIT · patricio0312rev/skills