i18n-validate
SolidValidate translation completeness and consistency across all locale files — detect missing keys, untranslated strings, format mismatches, and glossary violations.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- Fr-e-d
- Repository
- Fr-e-d/GAAI-framework
- Created
- 7 months ago
- Last Updated
- today
- Language
- Shell
- License
- NOASSERTION
Similar Skills
Semantically similar based on skill content — not just same category
i18n-integrity
Translation integrity: every key present in every language, no hardcoded strings, consistent placeholders and plurals. Runs when user-facing text changes.
i18n-check
Runs a comprehensive internationalization (i18n) and localization (l10n) readiness check across a project's web frontend, backend, and mobile app, then reports the results as one table (check, area, status, evidence, recommendation). Covers string externalization vs. hardcoded UI/backend text, translation completeness across all supported locales, correct pluralization (ICU MessageFormat/gettext ngettext/framework-native vs. naive English-only concatenation), sentence construction via string concatenation that breaks word order across languages, locale-aware date/time/number/currency/unit formatting vs. hardcoded formats, text-expansion and layout resilience for longer/shorter/differently-scripted translations, RTL (right-to-left) layout support for Arabic/Hebrew/Farsi/Urdu locales, character encoding (UTF-8 end-to-end) and font-fallback coverage for non-Latin scripts, locale detection/switching/persistence and regional-variant fallback chains (e.g. de-CH -> de -> default locale), translation-file/source-key
i18n
Handle internationalization (i18n) translation files and produce culturally authentic translations. Use when: (1) editing, creating, or modifying translation files (JSON, YAML, TypeScript, JS) — especially large ones that risk exceeding token limits; (2) translating UI strings into any supported language/dialect; (3) reviewing translations for cultural accuracy and naturalness; (4) syncing translation keys across multiple locale files; (5) adding new languages or regional variants to an existing i18n setup. Triggers on "translate", "i18n", "localization", "translation file", "locale", "add language", "translation keys", or any specific locale code (e.g., th, ja, ko, zh-CN, de, fr, es, it, zh-TW, zh-HK, th-bupphe). Does NOT trigger on defining or glossing a single word/phrase inside a sentence ("what does X mean here", "define X in context") — that is the `define` skill. This skill is for i18n files and shipping localized strings, not inline word-meaning lookups.