i18n-glossary-sync

Synchronize locale files with a markdown glossary and flag missing translations.

157|28|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Fr-e-d/GAAI-framework --skill i18n-glossary-sync-fr-e-d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-glossary-sync
Source: https://github.com/Fr-e-d/GAAI-framework/tree/main/.gaai/core/skills/cross/i18n-glossary-sync
Command: npx skills add https://github.com/Fr-e-d/GAAI-framework --skill i18n-glossary-sync-fr-e-d

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures consistency in internationalization (i18n) by synchronizing terms across all language translation files and a central glossary, preventing terminology drift and simplifying new language additions.

Core Features & Use Cases

  • Terminology Consistency: Enforces uniform use of domain-specific terms across all supported languages.
  • Drift Detection: Identifies and flags inconsistencies between glossary definitions and actual usage in translation files.
  • Missing Translation Alerts: Highlights terms present in the codebase but missing from the glossary for specific languages.
  • New Term Discovery: Automatically detects new terms introduced in translations and suggests adding them to the glossary.
  • Deprecated Term Management: Flags terms in the glossary that are no longer in use.
  • Use Case: After adding a new feature with terms like "lead" and "milestone," this skill verifies that these terms are correctly translated and consistently used in English, French, German, and Spanish, flagging any discrepancies or missing translations.

Quick Start

Run the i18n-glossary-sync skill to analyze translation files in the 'locales/' directory against the glossary at 'domains/i18n/glossary.md'.

Frequently Asked Questions about i18n-glossary-sync

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

FAQPage Schema
How do I sync i18n glossary terms across multiple language translation files?

To sync i18n glossary terms, run this skill to analyze your locale files against a central markdown glossary, detecting missing translations and synchronizing new terminology across all language pairs.

What causes terminology drift in localization and how do I detect it?

Terminology drift in localization occurs when translation files diverge from canonical definitions; this skill detects drift by flagging inconsistencies between your markdown glossary and actual term usage in locale files.

How do I flag missing translations for domain-specific terms in my locale files?

You can flag missing translations by running this skill to compare your codebase's locale files against the glossary, highlighting domain-specific terms that are absent for specific supported languages.

Can I use a markdown file as a canonical glossary for translation consistency?

Yes, you can use a markdown file as a canonical glossary; this skill analyzes locale files against a markdown-formatted glossary to enforce consistent terminology across all language pairs.

How do I manage deprecated terminology in my i18n translation workflow?

To manage deprecated terminology in your i18n workflow, this skill automatically flags glossary terms that are no longer in use within your locale translation files, simplifying glossary maintenance.

What is the best way to discover new terms introduced in software translations?

The best way to discover new translation terms is to use this skill to automatically detect new terminology introduced in your locale files and suggest adding them to the central glossary.