Detect untranslated keys in Futari's ja.ts using a kanji whitelist.
npx skills add https://github.com/redtear1115/oikos --skill ja-i18n
Please help me install this Agent Skill. Skill: ja-i18n Source: https://github.com/redtear1115/oikos/tree/main/.claude/skills/ja-i18n Command: npx skills add https://github.com/redtear1115/oikos --skill ja-i18n
Futari's ja.ts contains many kanji characters considered correct Japanese but can be flagged as untranslated if not carefully reviewed. This skill provides a structured process to detect truly untranslated keys, prevent false positives with a kanji whitelist, and maintain consistent, natural Japanese translations.
Load the kanji whitelist from references/kanji-whitelist.md, scan ja.ts for untranslated keys, and begin translating with proper Japanese.
High-intent search queries and answers about installing and using this skill.
To detect untranslated keys in Japanese localization files, scan ja.ts while cross-referencing a kanji whitelist to filter out valid Japanese characters, ensuring only truly untranslated entries are flagged for review.
Correct kanji gets flagged as untranslated when a kanji whitelist is not loaded during the review process. Maintaining and extending the kanji whitelist prevents these false positives and aligns terminology with Japanese UI standards.
Maintain consistent Japanese UI translations by auditing ja.ts for untranslated keys and guiding accurate translations using a kanji whitelist, ensuring natural Japanese phrasing and proper kanji usage across UI terms during ongoing maintenance.
A kanji whitelist is a reference list of valid Japanese characters used during localization to prevent false positives. You need it when scanning ja.ts files to distinguish between truly untranslated keys and correct kanji that might be incorrectly flagged.
Yes, you can use a kanji whitelist to extend terminology for ongoing Japanese localization reviews. The whitelist can be maintained and updated to align with Japanese UI terminology, reducing false positives and improving translation accuracy over time.
The main limitation of using a kanji whitelist for Japanese translation audits is that unmaintained whitelists may miss new kanji, causing false positives. Additionally, the whitelist only addresses kanji detection and does not automatically generate natural Japanese phrasing for UI terms.
wayne930242Validate Markdown terminology against a glossary and flag inconsistencies.
OpenAEC-FoundationValidates Fluent FTL syntax and React integration in TypeScript codebases.
xenitV1Audit codebases for hardcoded strings and missing translation keys.
RodrigoVeraCandiaImplement Angular 19+ i18n with @ngx-translate/core and dynamic language switching.
