# Automate Web App Localization

Adding multilingual support often scatters strings, routing, metadata, and locale files across the codebase. This skill plans and implements i18n setup with translations, validation, and documentation.

## Install

```bash
npx skillstore add dnyoussef/i18n-automation
```

## Metadata

- Status: approved
- Slug: dnyoussef-i18n-automation
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: 87e05714638dd9633ba724f02d1d76cdb435bdc3e5ba2653bc53db29cc293ca5
- Author: DNYoussef
- GitHub username: DNYoussef
- License: MIT
- Repository: https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/i18n-automation
- Ref: c579efd02184f1128d6741d16e6c8d951d7d4208
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 80
- Quality tier: silver
- Public page: https://skillstore.pages.dev/skills/dnyoussef-i18n-automation
- Manifest: https://skillstore.pages.dev/api/skills/dnyoussef-i18n-automation/manifest

## Capabilities

- Detects common web frameworks and selects next-intl, react-i18next, or vue-i18n guidance.
- Designs nested or flat translation key structures for pages and shared UI.
- Creates locale file plans for JSON, YAML, PO, or XLIFF workflows.
- Guides language switcher, locale routing, SEO metadata, and sitemap localization.
- Includes RTL checks for Arabic, Hebrew, and Persian layouts.

## Use Cases

- Launch Multilingual Pages: Add translated routes, metadata, and locale files for a marketing site.
- Prepare MVP Translations: Generate first-pass translations and validation tasks for a product release.
- Standardize Locale Structure: Create consistent key naming, file organization, and review steps across locales.

## Prompt Templates

### Translate Basic UI

```
Translate my React app to Spanish and French. Create a simple key structure and locale files for shared buttons and homepage text.
```

### Set Up Next.js i18n

```
Set up next-intl for my Next.js app with English, Japanese, and Arabic. Include routing, metadata, and a language switcher.
```

### Audit Existing Localization

```
Audit my existing i18n setup for missing keys, broken placeholders, RTL layout issues, and SEO gaps. Return prioritized fixes.
```

### Design Scalable Workflow

```
Design a scalable localization workflow with namespaces, fallback rules, translation review steps, and documentation for adding languages.
```

## Limitations

- AI translations still need native speaker review before production release.
- Package installation requires user approval in controlled environments.
- It does not replace a translation management system for large teams.
- Custom frameworks may need manual integration choices.

## Best Practices

- Keep translation keys stable and grouped by page or shared component.
- Preserve placeholders and plural rules during every translation pass.
- Review production translations with native speakers before release.

## Anti Patterns

- Do not mix hardcoded user-facing strings with translated UI.
- Do not use machine translations without review for legal or checkout flows.
- Do not ignore RTL layout testing when adding Arabic, Hebrew, or Persian.

## Security Audit

- Audited at: 2026-07-05T13:40:14.405\+00:00
- Summary: All static findings were reviewed as false positives. Alerts are Markdown code fences, inline template literals, example URLs, XML namespace references, and diagram edges. No prompt injection, data exfiltration, or malicious command execution intent was found in SKILL.md or i18n-automation-process.dot.

## Stats

- Views: 251
- Downloads: 10
- Favorites: 0
- Popularity score: 0