skills.rest
hdkz-dev
hdkz-devCOMMUNITY
Explore all skills by this author →
GitHub

i18n-guardian

Compare ja and en locale trees to report missing keys and hard-coded Japanese strings.

1|Updated Feb 6, 2026
Search Tags:#localization#translation#i18n#dictionary-sync#hardcode-detection
One-click install
npx skills add https://github.com/hdkz-dev/multi-game-engines --skill i18n-guardian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n-guardian
Source: https://github.com/hdkz-dev/multi-game-engines/tree/main/.agent/skills/i18n-guardian
Command: npx skills add https://github.com/hdkz-dev/multi-game-engines --skill i18n-guardian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps enforce strict multilingual rules (no hard-coded Japanese, keep ja/en dictionaries in sync), prevent translation mistakes, detect missing translation keys, and streamline translation-key management.

Core Features & Use Cases

  • Sync Check: Compare locales/ja and locales/en structures and keys, report missing keys and paths, and suggest commands like diff -r locales/ja locales/en or a script to recursively check keys.
  • Hardcode Detection: Scan app and components for Japanese (2-byte) strings, ignoring comments and console logs, and report hard-coded UI text.
  • Key Management: Guide and assist adding new translation keys to both ja and en dictionaries, respecting existing directory structure (e.g., locales/ja/...).

Quick Start

Run i18n-guardian to scan your localization files and identify translation gaps and hard-coded strings.

Frequently Asked Questions about i18n-guardian

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

FAQPage Schema
How do I detect hard-coded Japanese strings in my frontend codebase?▼

Locale dictionary synchronization compares ja and en locale trees to report missing keys and mismatched paths. It suggests recursive diff checks to ensure both locale structures match exactly and prevent missing translation entries.

How do I keep ja and en locale dictionaries in sync?▼

Locale dictionary synchronization compares ja and en locale trees to report missing keys and mismatched paths. It suggests recursive diff checks to ensure both locale structures match exactly and prevent missing translation entries.

What is the best way to add new translation keys to existing locale directories?▼

Hardcode detection works by scanning frontend app and component files for 2-byte Japanese characters, deliberately ignoring code comments and console log statements. It reports only hard-coded UI text that requires extraction into translation dictionaries.

Does hardcode detection ignore comments and console logs when scanning?▼

Hardcode detection works by scanning frontend app and component files for 2-byte Japanese characters, deliberately ignoring code comments and console log statements. It reports only hard-coded UI text that requires extraction into translation dictionaries.

Can I use i18n-guardian to check missing translation keys across multiple locales?▼

i18n-guardian is applied to frontend projects to detect hard-coded Japanese strings and enforce ja and en dictionary synchronization. It reports i18n inconsistencies, missing translation keys, and provides remediation guidance for locale files.

Related Skills

Explore More Software Engineering Skills→
Jij-IncJij-Inc
21

translate

Translate jupytext-formatted Python documentation from English to Japanese.

Official
Intermediate
DayoptDayopt

i18n

Generates translation keys and detects Chinese-language strings in code, supporting localization workflows.

Official
Advanced
QunnnnQunnnn

go-continuous-integration

Configure GitHub Actions CI pipelines for Go projects with testing, linting, and security scanning.

Community
Intermediate
Oscar-Ivan-SalasOscar-Ivan-Salas

i18n-localization

Audit React, Next.js, Vue, and Python code for hardcoded UI strings and i18n gaps.

Community
Intermediate