language-config

Configure multilingual brand settings in profile.json with language codes and formatting rules.

Updated May 18, 2026
One-click install
npx skills add https://github.com/ajayatwal1105-emerson/digital-marketing-pro --skill language-config-ajayatwal1105-emerson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: language-config
Source: https://github.com/ajayatwal1105-emerson/digital-marketing-pro/tree/main/skills/language-config
Command: npx skills add https://github.com/ajayatwal1105-emerson/digital-marketing-pro --skill language-config-ajayatwal1105-emerson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents repeated translation fixes and inconsistent localization by centralizing the brand’s language, do-not-translate terms, translation routing, and locale formatting rules.

Core Features & Use Cases

  • Multilingual configuration: Set a primary/source language, manage secondary/content target languages, and persist them in the active brand profile.
  • Do-not-translate enforcement: Maintain an exact list of protected terms (brand/product names, trademarks, technical phrases) to keep them unchanged across all languages.
  • Translation service routing: Assign preferred translation MCPs per language to override default routing logic.
  • Locale formatting control: Configure date, number, currency, and measurement formatting (with previews) for each language-region.

Quick Start

Configure your brand’s target markets and formatting by running the command /digital-marketing-pro:language-config and choosing the action set-primary, then enter your ISO language code (for example, en-US) when prompted.

Frequently Asked Questions about language-config

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

FAQPage Schema
How do I configure multilingual settings for a marketing brand?

Configure multilingual settings by setting a primary language, adding target languages, and persisting these fields in the active brand profile to keep downstream localization workflows consistent.

How do I manage do-not-translate terms for multilingual localization?

Manage do-not-translate terms by maintaining an exact list of protected brand and product names in batch, ensuring they remain unchanged across all target languages during translation routing.

How do I set locale-specific date and currency formatting for target languages?

Set locale formatting rules by configuring date, number, currency, and measurement formats for each language-region, generating previews to validate output before running downstream workflows.

Can I override translation routing services per language?

Yes, you can override default translation routing logic by assigning preferred translation MCPs to specific target languages within your saved brand profile configuration.

Do I need specific language codes for locale formatting control?

Yes, you must enter valid ISO language codes, such as en-US, to validate against supported routing logic and correctly apply locale-specific formatting rules.