ja-i18n

Detect untranslated keys in Futari's ja.ts using a kanji whitelist.

1|1|Updated May 2, 2026

Search Tags:#japanese #localization #translation #whitelist #kanji #ja-i18n #futari

Ready to run

npx skills add https://github.com/redtear1115/oikos --skill ja-i18n

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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.

Core Features & Use Cases

Audit ja.ts for untranslated keys and provide accurate Japanese translations that fit Futari's context.
Maintain and extend the kanji whitelist to minimize false positives and align terminology with Japanese UI.

Quick Start

Load the kanji whitelist from references/kanji-whitelist.md, scan ja.ts for untranslated keys, and begin translating with proper Japanese.

Frequently Asked Questions about ja-i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect untranslated keys in a Japanese localization file without false positives?▼

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.

Why does my Japanese translation review flag correct kanji as untranslated?▼

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.

How to maintain consistent Japanese UI translations for a TypeScript localization file?▼

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.

What is a kanji whitelist and when do I need it for Japanese localization?▼

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.

Can I use a kanji whitelist to extend terminology for ongoing Japanese localization reviews?▼

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.

What are the limitations of using a kanji whitelist for Japanese translation audits?▼

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.