# Audit and Improve Application Localization

Hardcoded text and incomplete locale files create inconsistent multilingual experiences. This skill reviews localization structure, detects common gaps, and recommends practical i18n patterns.

## Install

```bash
npx skillstore add sickn33/i18n-localization
```

## Metadata

- Status: approved
- Slug: sickn33-i18n-localization
- Skillstore revision: r2
- Version status: missing
- Tree hash: 3124477f6111ff46e8bfc304f96e46eeff2da2a545536075c5009ec811563850
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/i18n-localization
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- 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
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/sickn33-i18n-localization
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-i18n-localization/manifest

## Capabilities

- Detects common hardcoded strings in React, Vue, and Python source files.
- Finds JSON, PO, message, translation, locale, language, and i18n resource files.
- Compares flattened JSON translation keys across multiple locale directories.
- Reviews translation keys, namespaces, fallback behavior, pluralization, and locale-aware formatting.
- Provides implementation examples for react-i18next, next-intl, Python gettext, and RTL CSS.

## Use Cases

- Prepare a Web Application: Review components, locale files, formatting, and RTL behavior before a multilingual release.
- Check Translation Coverage: Compare locale key sets and identify missing or extra entries across supported languages.
- Establish i18n Standards: Define translation namespaces, fallback rules, formatting patterns, and release checks for a product team.

## Prompt Templates

### Find Hardcoded Text

```
Review [project path] for hardcoded user-facing text and list each likely issue with its file and recommended translation key.
```

### Compare Locale Keys

```
Compare locale files under [locale path], using [base locale] as the reference, and summarize missing or extra keys by language.
```

### Review Locale Behavior

```
Assess pluralization, date and number formatting, fallback behavior, and RTL support for [framework] and [supported locales].
```

### Plan an i18n Migration

```
Design a phased migration for [application], covering key structure, framework integration, locale resources, automated checks, fallback policy, and RTL testing.
```

## Limitations

- The checker scans at most 50 source files.
- Regex detection can miss dynamic text or report non-user-facing strings.
- Locale completeness comparison supports JSON files, not PO content.
- The skill does not create professional translations or validate linguistic quality.

## Best Practices

- Use stable translation keys grouped by feature namespace.
- Apply locale-aware plural, date, number, and currency formatting.
- Test fallback locales, long text, and RTL layouts before release.

## Anti Patterns

- Do not concatenate translated fragments into complete sentences.
- Do not assume every language uses the same text length or direction.
- Do not treat automated key checks as linguistic quality review.

## Security Audit

- Audited at: 2026-07-24T00:47:54.552\+00:00
- Summary: All 13 static findings are false positives after source review. The high findings confuse Python dictionary keys with certificate files. The medium findings identify Markdown fences and inline command documentation, not executable Ruby or shell backticks.

## Stats

- Views: 108
- Downloads: 8
- Favorites: 0
- Popularity score: 0