localization-engineer · daffy0208 — Claude Code skill: what it does
localization-engineer — a skill for internationalizing Next.js apps with next-intl. Helps set up translations, plural rules, date or currency formatting, and RTL layouts.
MIT 163 installs ★ 39 updated 2025-12-25
npx skills add daffy0208/ai-dev-standards --skill localization-engineer -a claude-codeWhat localization-engineer does
The skill guides internationalization setups using next-intl in Next.js. It provides ready configurations for getRequestConfig, route matching inside middleware.ts, and translation dictionaries in JSON format. It shows string usage across both client components with useTranslations and React Server Components.
Inside are patterns for date, time, currency, and number formatting via useFormatter, plus ICU pluralization rules. It also covers right-to-left layout adjustments with dir="rtl" and CSS logical properties such as margin-inline-start. Locale detection checks query parameters, local storage, and browser language.
Your project needs Next.js with next-intl installed to apply these templates directly.
What it helps with
- configure multilingual routing and middleware in Next.js
- organize translations into structured JSON files
- format dates, times, and currencies according to user locale
- adapt layouts for right-to-left (RTL) reading with logical CSS properties
Example prompts for the agent
- Set up Next.js localization using next-intl
- Add a language switcher and RTL support for Arabic
- Format currency and dates for en, es, and ja locales
How to install localization-engineer
1Skills CLI (Vercel)
npx skills add daffy0208/ai-dev-standards --skill localization-engineer -a claude-code2Manually: put the files in place
~/.claude/skills/localization-engineer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/localization-engineer/
1Skills CLI (Vercel)
npx skills add daffy0208/ai-dev-standards --skill localization-engineer -a codex2Manually: put the files in place
.agents/skills/localization-engineer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add daffy0208/ai-dev-standards --skill localization-engineer -a cursor2Manually: put the files in place
.cursor/skills/localization-engineer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install daffy0208/ai-dev-standards skills/localization-engineer2Manually: put the files in place
.github/skills/localization-engineer/SKILL.md1Skills CLI (Vercel)
npx skills add daffy0208/ai-dev-standards --skill localization-engineer -a gemini-cli2Platform CLI
gemini skills install https://github.com/daffy0208/ai-dev-standards --path skills/localization-engineerManually: put the files in place
.devin/skills/localization-engineer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add daffy0208/ai-dev-standards --skill localization-engineer -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 localization-engineer
How to install localization-engineer in Claude Code?
Run npx skills add daffy0208/ai-dev-standards --skill localization-engineer -a claude-code. The file will be placed in ~/.claude/skills/localization-engineer/SKILL.md.
What does localization-engineer do?
It equips the assistant with patterns for app internationalization, covering middleware setup, message files, RTL styling, and locale-based formatting.
Which translation library does this skill rely on?
All instructions and code samples in this skill are designed around Next.js and the next-intl package.
Source text
SKILL.md · MIT
---
name: localization-engineer
description: Expert in internationalization (i18n), multi-language support, and localization
version: 1.0.0
tags: [i18n, localization, translation, multilingual, internationalization]
---
# Localization Engineer Skill
I help you build multilingual applications with proper internationalization (i18n) and localization (l10n) support.
## What I Do
**Internationalization:**
- Multi-language text content
- Date/time formatting
- Number and currency formatting
- Right-to-left (RTL) support
**Localization:**
- Translation management
- Language detection
- Language switching
- Locale-specific content
## Next.js Internationalization
### Setup with next-intl
```bash
npm install next-intl
```
```typescript
// i18n/request.ts
import { getRequestConfig } from 'next-intl/server'
export default getRequestConfig(async ({ locale }) => ({
messages: (await import(`../messages/${locale}.json`)).default
}))
```
```typescript
// middleware.ts
import createMiddleware from 'next-intl/middleware'
export default createMiddleware({
locales: ['en', 'es', 'fr', 'de', 'ja'],
defaultLocale: 'en'
})
export const config = {
matcher: ['/((?!api|_next|.*\\..*).*)']
}
```
### Translation Files
```json
// messages/en.json
{
"common": {
"welcome": "Welcome",
"loading": "Loading...",
"error": "Something went wrong"
},
"navigation": {
"home": "Home",
"about": "About",
"contact": "Contact"
},
"auth": {
"login": "Log in",
"logout": "Log out",
"signUp": "Sign up",
"emailPlaceholder": "Enter your email",
"passwordPlaceholder": "Enter your password"
}
}
```
```json
// messages/es.json
{
"common": {
"welcome": "Bienvenido",
"loading": "Cargando...",
"error": "Algo salió mal"
},
"navigation": {
"home": "Inicio",
"about": "Acerca de",
"contact": "Contacto"
},
"auth": {
"login": "Iniciar sesión",
"logout": "Cerrar sesión",
"signUp": "Registrarse",
"emailPlaceholder": "Ingrese su correo electrónico",
"passwordPlaceholder": "Ingrese su contraseña"
}
}
```
---
## Using Translations
### Client Component
```typescript
'use client'
import { useTranslations } from 'next-intl'
export function LoginForm() {
const t = useTranslations('auth')
return (
<form>
<input
type="email"
placeholder={t('emailPlaceholder')}
/>
<input
type="password"
placeholder={t('passwordPlaceholder')}
/>
<button>{t('login')}</button>
</form>
)
}
```
### Server Component
```typescript
import { useTranslations } from 'next-intl'
export default function HomePage() {
const t = useTranslations('common')
return (
<div>
<h1>{t('welcome')}</h1>
</div>
)
}
```
---
## Language Switcher
```typescript
'use client'
import { useLocale } from 'next-intl'
import { useRouter, usePathname } from 'next/navigation'
const languages = [
{ code: 'en', name: 'English', flag: '🇺🇸' },
{ code: 'es', name: 'Español', flag: '🇪🇸' },
{ code: 'fr', name: 'Français', flag: '🇫🇷' },
{ code: 'de', name: 'Deutsch', flag: '🇩🇪' },
{ code: 'ja', name: '日本語', flag: '🇯🇵' }
]
export function LanguageSwitcher() {
const locale = useLocale()
const router = useRouter()
const pathname = usePathname()
const switchLanguage = (newLocale: string) => {
// Remove current locale from pathname
const pathWithoutLocale = pathname.replace(`/${locale}`, '')
// Navigate to new locale
router.push(`/${newLocale}${pathWithoutLocale}`)
}
return (
<select
value={locale}
onChange={(e) => switchLanguage(e.target.value)}
className="px-4 py-2 border rounded"
>
{languages.map((lang) => (
<option key={lang.code} value={lang.code}>
{lang.flag} {lang.name}
</option>
))}
</select>
)
}
```
---
## Date and Time Formatting
```typescript
'use client'
import { useFormatter } from 'next-intl'
export function FormattedDate({ date }: { date: Date }) {
const format = useFormatter()
return (
<div>
{/* Full date */}
<p>{format.dateTime(date, { dateStyle: 'full' })}</p>
{/* Short date */}
<p>{format.dateTime(date, { dateStyle: 'short' })}</p>
{/* Custom format */}
<p>{format.dateTime(date, {
year: 'numeric',
month: 'long',
day: 'numeric',
hour: 'numeric',
minute: 'numeric'
})}</p>
{/* Relative time */}
<p>{format.relativeTime(date)}</p>
</div>
)
}
// Examples:
// en: "Monday, October 22, 2025"
// es: "lunes, 22 de octubre de 2025"
// ja: "2025年10月22日月曜日"
```
---
## Number and Currency Formatting
```typescript
'use client'
import { useFormatter } from 'next-intl'
export function FormattedNumber({ value }: { value: number }) {
const format = useFormatter()
return (
<div>
{/* Number */}
<p>{format.number(value)}</p>
{/* Currency */}
<p>{format.number(value, { style: 'currency', currency: 'USD' })}</p>
{/* Percentage */}
<p>{format.number(value / 100, { style: 'percent' })}</p>
{/* Compact notation */}
<p>{format.number(value, { notation: 'compact' })}</p>
</div>
)
}
// Examples:
// en: "1,234.56" "$1,234.56" "12%" "1.2K"
// de: "1.234,56" "1.234,56 $" "12 %" "1200"
// ja: "1,234.56" "$1,234.56" "12%" "1.2千"
```
---
## Pluralization
```json
// messages/en.json
{
"items": {
"count": "{count, plural, =0 {No items} one {# item} other {# items}}"
}
}
```
```typescript
'use client'
import { useTranslations } from 'next-intl'
export function ItemCounter({ count }: { count: number }) {
const t = useTranslations('items')
return <p>{t('count', { count })}</p>
}
// count = 0: "No items"
// count = 1: "1 item"
// count = 5: "5 items"
```
---
## RTL (Right-to-Left) Support
```typescript
// app/[locale]/layout.tsx
import { useLocale } from 'next-intl'
const rtlLanguages = ['ar', 'he', 'fa']
export default function LocaleLayout({ children }) {
const locale = useLocale()
const isRTL = rtlLanguages.includes(locale)
return (
<html lang={locale} dir={isRTL ? 'rtl' : 'ltr'}>
<body>{children}</body>
</html>
)
}
```
**RTL CSS:**
```css
/* Automatically flips for RTL */
.container {
margin-inline-start: 1rem; /* Use logical properties */
padding-inline-end: 1rem;
}
/* Manual RTL handling */
[dir='rtl'] .menu {
left: auto;
right: 0;
}
```
---
## Language Detection
```typescript
// lib/detect-locale.ts
export function detectUserLocale(): string {
// 1. Check URL parameter
const urlParams = new URLSearchParams(window.location.search)
const urlLocale = urlParams.get('lang')
if (urlLocale) return urlLocale
// 2. Check localStorage
const savedLocale = localStorage.getItem('preferredLocale')
if (savedLocale) return savedLocale
// 3. Check browser language
const browserLocale = navigator.language.split('-')[0]
return browserLocale
// 4. Default
return 'en'
}
```
---
## Translation with Variables
```json
// messages/en.json
{
"welcome": "Welcome, {name}!",
"itemsInCart": "You have {count} {count, plural, one {item} other {items}} in your cart",
"priceDisplay": "Price: {price, number, ::currency/USD}"
}
```
```typescript
'use client'
import { useTranslations } from 'next-intl'
export function Greeting({ userName }: { userName: string }) {
const t = useTranslations()
return (
<div>
<h1>{t('welcome', { name: userName })}</h1>
<p>{t('itemsInCart', { count: 3 })}</p>
<p>{t('priceDisplay', { price: 49.99 })}</p>
</div>
)
}
// Output:
// "Welcome, John!"
// "You have 3 items in your cart"
// "Price: $49.99"
```
---
## Locale-Specific Content
```typescript
// app/[locale]/page.tsx
import { useLocale } from 'next-intl'
export default function HomePage() {
const locale = useLocale()
const content = {
en: {
hero: 'Build amazing apps',
description: 'The best platform for developers'
},
es: {
hero: 'Crea aplicaciones increíbles',
description: 'La mejor plataforma para desarrolladores'
},
ja: {
hero: '素晴らしいアプリを作成',
description: '開発者のための最高のプラットフォーム'
}
}
return (
<div>
<h1>{content[locale].hero}</h1>
<p>{content[locale].description}</p>
</div>
)
}
```
---
## Translation Management
### Using Translation Service (Lokalise, Crowdin)
```typescript
// scripts/sync-translations.ts
async function syncTranslations() {
// Download translations from service
const response = await fetch('https://api.lokalise.com/api2/projects/PROJECT_ID/files/download', {
headers: {
'X-Api-Token': process.env.LOKALISE_API_KEY!
}
})
const data = await response.json()
// Save to messages folder
await fs.writeFile('./messages/en.json', JSON.stringify(data.en, null, 2))
console.log('Translations synced!')
}
```
---
## Missing Translation Handling
```typescript
// i18n/request.ts
import { getRequestConfig } from 'next-intl/server'
export default getRequestConfig(async ({ locale }) => ({
messages: (await import(`../messages/${locale}.json`)).default,
onError: error => {
console.error('Translation error:', error)
},
getMessageFallback: ({ namespace, key, error }) => {
return `${namespace}.${key}` // Show key if translation missing
}
}))
```
---
## SEO for Multilingual Sites
```typescript
// app/[locale]/layout.tsx
import { useLocale } from 'next-intl'
export async function generateMetadata({ params: { locale } }) {
const t = await useTranslations('metadata')
return {
title: t('title'),
description: t('description'),
alternates: {
canonical: `/${locale}`,
languages: {
en: '/en',
es: '/es',
fr: '/fr',
de: '/de',
ja: '/ja'
}
}
}
}
```
**HTML Output:**
```html
<link rel="canonical" href="https://example.com/en" />
<link rel="alternate" hreflang="en" href="https://example.com/en" />
<link rel="alternate" hreflang="es" href="https://example.com/es" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr" />
```
---
## When to Use Me
**Perfect for:**
- Building multilingual applications
- International product launches
- Global SaaS platforms
- E-commerce in multiple countries
- Content management systems
**I'll help you:**
- Set up i18n infrastructure
- Manage translations
- Format dates, numbers, currencies
- Handle RTL languages
- Optimize for SEO
## What I'll Create
```
🌍 Multi-Language Support
📅 Date/Time Formatting
💰 Currency Formatting
🔄 Language Switching
📝 Translation Management
🌐 RTL Support
```
Let's make your app globally accessible!
© daffy0208 · MIT · daffy0208/ai-dev-standards
Similar skills
All skills for Frontend and UI →localization-engineer by other authors comes first.