localization-testing — Claude Code skill: tests and install
The localization-testing skill checks translation coverage, locale-specific formats, RTL layouts, and Unicode handling. Use it when adding languages or preparing an international release.
MIT 137 installs ★ 533 updated 2026-10-25
npx skills add proffesor-for-testing/agentic-qe --skill localization-testing -a claude-codeWhat localization-testing does
The skill helps find untranslated strings and text embedded in code, then checks dates, times, and currencies against locale-specific expectations. It also covers right-to-left layouts for Arabic and Hebrew, plus Unicode characters in user input. These checks fit before an international release or after UI changes.
For browser-based RTL comparisons, language-switching flows, and screenshots, the instructions route testing through the qe-browser skill. Examples compare translation key sets, inspect the page’s dir attribute, and verify saved characters. Agent-driven checks can involve qe-test-generator, qe-test-executor, and qe-visual-tester, with a URL, locales, and check types as inputs.
This skill covers testing, not translating content. Browser visual checks rely on qe-browser; without that skill, the documented browser workflow cannot run.
What it helps with
- find strings missing from locale files
- check date and currency formatting by locale
- spot UI text embedded in code
- verify RTL direction in navigation and icons
- confirm fields preserve Unicode characters
Example prompts for the agent
- Check translation coverage and locale formats in my app for
en-US,fr-FR, andde-DE. - Test the Arabic RTL layout and find UI text embedded in code.
- Verify that profile fields preserve Unicode characters.
How to install localization-testing
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill localization-testing -a claude-code2Manually: put the files in place
~/.claude/skills/localization-testing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/localization-testing/
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill localization-testing -a codex2Manually: put the files in place
.agents/skills/localization-testing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill localization-testing -a cursor2Manually: put the files in place
.cursor/skills/localization-testing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install proffesor-for-testing/agentic-qe assets/skills/localization-testing2Manually: put the files in place
.github/skills/localization-testing/SKILL.md1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill localization-testing -a gemini-cli2Platform CLI
gemini skills install https://github.com/proffesor-for-testing/agentic-qe --path assets/skills/localization-testingManually: put the files in place
.devin/skills/localization-testing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill localization-testing -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-testing
How do I install localization-testing in Claude Code?
Run npx skills add proffesor-for-testing/agentic-qe --skill localization-testing -a claude-code. The skill file is at ~/.claude/skills/localization-testing/SKILL.md.
What does localization-testing do?
It helps test translation coverage, locale-specific date and currency formats, RTL layout, and Unicode support. It can also check for strings embedded in code.
Does it need another skill for browser-based RTL checks?
Yes. The instructions direct browser RTL comparisons, language-switching checks, and screenshots to the qe-browser skill.
Source text
SKILL.md · MIT
---
name: localization-testing
description: "Internationalization (i18n) and localization (l10n) testing for global products including translations, locale formats, RTL languages, and cultural appropriateness. Use when launching in new markets or building multi-language products."
category: specialized-testing
priority: medium
tokenEstimate: 800
agents: [qe-test-generator, qe-test-executor, qe-visual-tester]
implementation_status: optimized
optimization_version: 1.0
last_optimized: 2025-12-02
dependencies: []
quick_reference_card: true
tags: [localization, i18n, l10n, translation, rtl, unicode, locale]
trust_tier: 3
validation:
schema_path: schemas/output.json
validator_path: scripts/validate-config.json
eval_path: evals/localization-testing.yaml
---
# Localization & Internationalization Testing
## Browser engine
Browser-driven locale checks (RTL layout diffs, language-switching flows, locale-specific screenshots) should go through the **qe-browser** fleet skill. Example:
```bash
vibium go "$BASE_URL?lang=ar" # Arabic, RTL
vibium wait load
node .claude/skills/qe-browser/scripts/visual-diff.js --name homepage-ar-rtl
vibium go "$BASE_URL?lang=ja" # Japanese, CJK text expansion
node .claude/skills/qe-browser/scripts/visual-diff.js --name homepage-ja
```
See `.claude/skills/qe-browser/SKILL.md` for the full reference.
<default_to_action>
When testing multi-language/region support:
1. VERIFY translation coverage (all strings translated)
2. TEST locale-specific formats (date, time, currency, numbers)
3. VALIDATE RTL layout (Arabic, Hebrew)
4. CHECK character encoding (UTF-8, unicode)
5. CONFIRM cultural appropriateness (icons, colors, content)
**Quick i18n Checklist:**
- All user-facing strings externalized
- No hardcoded text in code
- Date/time/currency formatted per locale
- RTL languages flip layout correctly
- Unicode characters display properly
**Critical Success Factors:**
- Don't hardcode strings - externalize everything
- Test with real speakers, not just translation files
- RTL requires mirrored UI layout
</default_to_action>
## Quick Reference Card
### When to Use
- Launching in new markets
- Adding language support
- Before international releases
- After UI changes
---
## Translation Coverage Testing
```javascript
test('all strings are translated', () => {
const enKeys = Object.keys(translations.en);
const frKeys = Object.keys(translations.fr);
const esKeys = Object.keys(translations.es);
// All locales have same keys
expect(frKeys).toEqual(enKeys);
expect(esKeys).toEqual(enKeys);
});
test('no missing translation placeholders', async ({ page }) => {
await page.goto('/?lang=fr');
const text = await page.textContent('body');
// Should not see placeholder keys
expect(text).not.toContain('translation.missing');
expect(text).not.toMatch(/\{\{.*\}\}/); // {{key}} format
});
```
---
## Date/Time/Currency Formats
```javascript
test('date formats by locale', () => {
const date = new Date('2025-10-24');
expect(formatDate(date, 'en-US')).toBe('10/24/2025');
expect(formatDate(date, 'en-GB')).toBe('24/10/2025');
expect(formatDate(date, 'ja-JP')).toBe('2025/10/24');
});
test('currency formats by locale', () => {
const amount = 1234.56;
expect(formatCurrency(amount, 'en-US', 'USD')).toBe('$1,234.56');
expect(formatCurrency(amount, 'de-DE', 'EUR')).toBe('1.234,56 €');
expect(formatCurrency(amount, 'ja-JP', 'JPY')).toBe('¥1,235');
});
```
---
## RTL (Right-to-Left) Testing
```javascript
test('layout flips for RTL languages', async ({ page }) => {
await page.goto('/?lang=ar'); // Arabic
const dir = await page.locator('html').getAttribute('dir');
expect(dir).toBe('rtl');
// Navigation should be on right
const nav = await page.locator('nav');
const styles = await nav.evaluate(el =>
window.getComputedStyle(el)
);
expect(styles.direction).toBe('rtl');
});
test('icons/images appropriate for RTL', async ({ page }) => {
await page.goto('/?lang=he'); // Hebrew
// Back arrow should point right in RTL
const backIcon = await page.locator('.back-icon');
expect(await backIcon.getAttribute('class')).toContain('rtl-flipped');
});
```
---
## Unicode Character Support
```javascript
test('supports unicode characters', async ({ page }) => {
// Japanese
await page.fill('#name', '山田太郎');
await page.click('#submit');
const saved = await db.users.findOne({ /* ... */ });
expect(saved.name).toBe('山田太郎');
// Arabic
await page.fill('#name', 'محمد');
// Emoji
await page.fill('#bio', '👋🌍');
expect(saved.bio).toBe('👋🌍');
});
```
---
## Agent-Driven Localization Testing
```typescript
// Comprehensive localization validation
await Task("Localization Testing", {
url: 'https://example.com',
locales: ['en-US', 'fr-FR', 'de-DE', 'ja-JP', 'ar-SA'],
checks: ['translations', 'formats', 'rtl', 'unicode'],
detectHardcodedStrings: true
}, "qe-test-generator");
// Returns:
// {
// locales: 5,
// missingTranslations: 3,
// formatIssues: 1,
// rtlIssues: 0,
// hardcodedStrings: ['button.submit', 'header.title']
// }
```
---
## Agent Coordination Hints
### Memory Namespace
```
aqe/localization-testing/
├── translations/* - Translation coverage
├── formats/* - Locale-specific formats
├── rtl-validation/* - RTL layout checks
└── unicode/* - Character encoding tests
```
### Fleet Coordination
```typescript
const l10nFleet = await FleetManager.coordinate({
strategy: 'localization-testing',
agents: [
'qe-test-generator', // Generate l10n tests
'qe-test-executor', // Execute across locales
'qe-visual-tester' // RTL visual validation
],
topology: 'parallel'
});
```
---
## Related Skills
- [accessibility-testing](../accessibility-testing/) - Language accessibility
- [compatibility-testing](../compatibility-testing/) - Cross-platform i18n
- [visual-testing-advanced](../visual-testing-advanced/) - RTL visual regression
---
## Remember
**With Agents:** Agents validate translation coverage, detect hardcoded strings, test locale-specific formatting, and verify RTL layouts automatically across all supported languages.
© proffesor-for-testing · MIT · proffesor-for-testing/agentic-qe