i18n-glossary-sync

Synchronize i18n glossary terms across language translation files.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/bketelsen/truenas-mcp --skill i18n-glossary-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-glossary-sync
Source: https://github.com/bketelsen/truenas-mcp/tree/main/.gaai/core/skills/cross/i18n-glossary-sync
Command: npx skills add https://github.com/bketelsen/truenas-mcp --skill i18n-glossary-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures consistency in your internationalization (i18n) efforts by synchronizing your glossary with actual usage in translation files, preventing terminology drift and ensuring accurate translations across all languages.

Core Features & Use Cases

  • Terminology Consistency: Enforces the use of defined terms across all language versions of your application.
  • Drift Detection: Identifies when terms used in translations do not match the official glossary.
  • Missing Translation Flags: Highlights terms present in the glossary but missing in specific language files.
  • New Term Discovery: Automatically finds new terms used in the codebase that are not yet in the glossary.
  • Use Case: After a new feature is released, this skill can scan all translation files for English, French, German, and Spanish, compare them against your central glossary, and report any inconsistencies or missing translations, providing actionable recommendations for the localization team.

Quick Start

Run the i18n-glossary-sync skill to analyze translation files in the 'locales/' directory against the glossary at 'domains/i18n/glossary.md' for English, French, German, and Spanish languages.

Frequently Asked Questions about i18n-glossary-sync

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

FAQPage Schema
How do I prevent terminology drift in my i18n translation files?

To prevent terminology drift, you can synchronize your translation files against a central glossary to detect inconsistent terms, flag missing translations, and enforce consistent terminology across all language pairs in your codebase.

What is the best way to find missing translations across multiple language pairs?

The best way to find missing translations is to analyze your locales path and glossary path to highlight terms present in the glossary but absent in specific language files, ensuring complete i18n coverage and accurate translations.

How do I keep my localization glossary updated with new codebase terms?

You can keep your localization glossary updated by scanning your translation files to automatically discover new terms used in the codebase that are not yet defined in your canonical glossary, and then synchronizing them across all languages.

Can I enforce consistent terminology across English, French, German, and Spanish locales?

Yes, you can enforce consistent terminology across specified languages like English, French, German, and Spanish by comparing actual usage in translation files against your central glossary and reporting inconsistencies for the localization team to fix.

Why does my application show inconsistent translations after a new feature release?

Inconsistent translations after a new feature release often happen because new terms were added to translation files without updating the central glossary, causing terminology drift that can be detected by synchronizing your glossary with actual usage.

Do I need a specific locales directory structure to check for missing translations?

You need a standard locales directory containing your translation files and a canonical glossary file to check for missing translations, allowing the skill to analyze the specified languages and report any terminology inconsistencies accurately.