glossary-builder
Build a translation/terminology glossary so a product's key terms render consistently everywhere. Use when asked to create a glossary, a termbase, a do-not-translate list, or to keep terminology consistent across translators/locales. Produces a glossary — each source term with its approved translation per locale, part of speech, definition/context, and do-not-translate flags — ready for a CAT tool or style guide.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill glossary-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Glossary Builder Skill Inconsistent terminology is the most visible localization failure — when "dashboard" is translated three ways across one product, it looks amateur and confuses users. A glossary (termbase) fixes the key terms *once*, so every translator and every locale uses the approved rendering. This skill builds it: extract the terms that matter, define them in context, and set the approved translation (or do-not-translate flag). ## Required Inputs Ask for these only if they aren't already provided: - **The source material / domain** — product UI, docs, or a term list; and the field (so definitions are right). - **Target locale(s)** — which languages need approved translations. - **Existing decisions** — any brand terms, product names, or prior translations to lock in. - **Do-not-translate candidates** — brand/product names, trademarks, code/API terms. ## Output Format ### Glossary: [product/domain] A termbase table — one row per term: | Source term | Part of speech | Definition / context | Do-not-translate? | [Locale 1] | [Locale 2] | |---|---|---|---|---|---| | Dashboard | noun | the main metrics screen | no | 仪表板 | Tableau de bord | | Acme Cloud | proper noun | produ
- Required Inputs
- Output Format
- Glossary: [product/domain]
- Quality Checks
- Anti-Patterns
- Based On
What does the glossary-builder skill do?
Build a translation/terminology glossary so a product's key terms render consistently everywhere. Use when asked to create a glossary, a termbase, a do-not-translate list, or to keep terminology consistent across translators/locales. Produces a glossary — each source term with its approved translation per locale, part of speech, definition/context, and do-not-translate flags — ready for a CAT tool or style guide.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill glossary-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.