idiomatique-translate

Translate strings idiomatically across target languages using project glossaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of translating text accurately and naturally across multiple languages, ensuring cultural relevance, consistent tone, and domain-specific terminology.

Core Features & Use Cases

  • Idiomatic Translation: Translates text to sound like a native speaker, not a literal translation.
  • Glossary & Tone Preservation: Uses project glossaries and defined tones to maintain brand voice.
  • Use Case: Translate UI copy for a global SaaS product, ensuring that error messages, button labels, and help text are not only grammatically correct but also culturally appropriate and tonally consistent across English, French, and German.

Quick Start

Translate the following English string into French, using the provided glossary and a transparent tone.

Frequently Asked Questions about idiomatique-translate

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

FAQPage Schema
How do I translate UI copy idiomatically across multiple languages?

To translate UI copy idiomatically, bulk process strings using a project glossary to ensure native phrasing while preserving tone, domain terminology, and format placeholders. This approach adapts text contextually for audience and regional preferences.

Does multilingual translation preserve format placeholders and brand tone?

Multilingual translation preserves format placeholders and brand tone by applying a defined project glossary during processing. This ensures consistent domain terminology and culturally appropriate voice across target languages for global SaaS products.

Can I bulk translate error messages and help text using a project glossary?

You can bulk translate error messages and help text using a project glossary. The process supports automatic source language detection and context-aware adaptation to maintain domain terminology, audience relevance, and regional preferences.

What is the best way to handle localization for domain-specific terminology?

The best way to handle localization for domain-specific terminology is using a project glossary during translation. This ensures consistent domain terminology and brand tone are maintained across multiple target languages while flagging untranslatable content.

Why does literal translation fail for internationalized software strings?

Literal translation fails for internationalized software strings because it ignores cultural relevance and native phrasing. Idiomatic translation solves this by using a glossary and tone definitions to adapt text contextually for audience and regional preferences.

Are there limitations when translating untranslatable content in a glossary?

A limitation of glossary-driven translation is handling untranslatable content. The process flags untranslatable strings rather than forcing a translation, ensuring domain terminology and format placeholders remain intact across target languages.