i18n-string-add

To add Korean and English UI strings simultaneously, update matching keys in both frontend/messages/ko.json and frontend/messages/en.json. This synchronized key creation ensures both locales stay aligned and the JSON structure is validated for the frontend build.

Preventing translation drift between ko.json and en.json files requires automatically updating matching keys in both locales. This approach checks for missing keys and reports conflicts or incomplete translations for quick resolution during localization updates.

Validating missing translation keys in TypeScript frontend localization files involves checking both ko.json and en.json for matching paths. The process identifies incomplete translations and reports conflicts so you can resolve them before building the frontend.

You can update existing localization keys in ko.json and en.json without breaking the JSON structure by applying synchronized updates. The Skill reads both files, updates matching keys, and validates the resulting JSON structure to ensure it is ready for a build.

Korean and English UI strings fall out of sync when new labels are added manually to only one locale. Coordinating localization across ko.json and en.json automatically propagates translation keys to both files, preventing drift and reducing manual edits.