idiomatique-translate

Name: idiomatique-translate
Availability: InStock
Author: petrsimonidesxart

Translate strings idiomatically across target languages using a project glossary.

Updated Mar 8, 2026

Search Tags:#localization #glossary #multilingual #tone-preservation #idiomatic-translation #domain-terminology

Ready to run

npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill idiomatique-translate-petrsimonidesxart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: idiomatique-translate
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/cross/idiomatique-translate
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill idiomatique-translate-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating content across languages is often literal, tone-deaf, and inconsistent with domain terminology. This skill automates idiomatic translations by leveraging a project glossary to preserve tone, domain terms, and placeholders while flagging content that cannot be translated reliably.

Core Features & Use Cases

Glossary-driven translation that enforces terminology consistency across languages.
Automatic source language detection and translation to multiple target languages.
Tone adaptation for domains like billing, marketing, and product UI, with placeholders preserved.
Flagging of terms that require glossary updates to improve future translations.

Quick Start

Provide a source string, target language, and optional glossary context to receive an idiomatic translation across languages.

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 while preserving format placeholders and domain terminology?▼

Idiomatic translation uses a project glossary to map domain terminology and preserve format placeholders across multiple target languages. It automatically detects the source language and adapts tone for UI copy, ensuring localization consistency without losing technical context.

What is the best way to maintain consistent terminology across multilingual localization projects?▼

Glossary-driven translation enforces terminology consistency by applying project glossary mappings across all target languages. It flags terms needing glossary updates during batch processing, maintaining consistent localization standards throughout onboarding and help texts.

Can I adapt translation tone for different contexts like billing, marketing, and product UI?▼

Context-aware tone adaptation supports domains like billing, marketing, and product UI during multilingual translation. The skill applies glossary mappings while adjusting tone to fit each domain, producing idiomatic translations suitable for varied content contexts.

Does idiomatic translation automatically detect the source language for batch processing?▼

Automatic source language detection enables batch processing of strings for idiomatic translation into multiple target languages. The skill applies glossary mappings and tone adaptation across all detected source content, flagging untranslatable terms for glossary updates.

Why does my multilingual translation flag certain terms as untranslatable?▼

Untranslatable content is flagged when terms lack corresponding mappings in the project glossary. These flags indicate terms requiring glossary updates to maintain consistent localization standards and ensure future translations preserve domain terminology accurately.

Do I need a project glossary to get idiomatic translations for onboarding and help texts?▼

A project glossary is required to enforce terminology consistency and preserve domain terms during idiomatic translation. Providing a source string, target language, and optional glossary context produces translations suitable for onboarding and help texts across multiple languages.