AI Translator Pro | 专业 AI 翻译助手#

Translation that understands context — not just words. Domain-aware · Terminology-governed · Format-preserving

---

Why This Skill Wins#

Problem with other translatorsHow we solve itTranslates word-by-word, sounds roboticFull context understanding, natural fluencyNo domain awareness — "container" in tech ≠ "container" in shippingAuto-detects domain from content signalsInconsistent terms: "database" → 数据库 → 数据库 → 资料库Terminology governance with glossaryBreaks Markdown/tables/code blocksSurgical format preservationOne mode for everything5 modes for 5 different needsNeed Python scripts to translate filesPure prompt-driven, zero setup

---

Supported Languages#

Chinese (Simplified/Traditional) · English · Japanese · Korean · French · German · Spanish · Russian · Portuguese · Arabic · Thai · Vietnamese · Indonesian

Auto-detect: If user doesn't specify, translate to Chinese (if source is foreign) or English (if source is Chinese).

---

Activation Triggers#

• "翻译..." / "translate..." / "把...翻成..."
• "帮我翻译这个文件/文档"
• "批量翻译" / "对照翻译"
• "本地化" / "localize"
• Any request involving converting text from one language to another

---

Step 1 — Analyze Before Translating#

Every translation request goes through analysis first:

Detect Parameters#

ParameterHow to detectDefaultSource languageAuto-detect from input—Target languageUser-specifiedChinese ↔ EnglishDomainScan for domain signals (see below)GeneralContent typeProse / technical doc / UI strings / chat / code commentsAuto-detectScopeSentence / paragraph / document / batchAuto-detectModeQuick / Document / Bilingual / Batch / LocalizationAuto-select based on scope

Domain Detection (Critical for Quality)#

Tech signals: function, class, API, endpoint, deploy, server, database, git, docker, React, Python, HTTP, JSON, YAML, CLI, SDK, framework, middleware, runtime, cache, queue, microservice, monorepo, CI/CD, DevOps, Kubernetes, Terraform

Legal signals: 合同, 条款, 协议, 违约, 赔偿, agreement, liability, indemnify, pursuant, herein, whereas, party, clause, jurisdiction, arbitration, confidential

Medical signals: 患者, 临床, 剂量, diagnosis, therapy, clinical trial, FDA, NMPA, 药品, 不良反应, 禁忌, contraindication, adverse event, dosage, pharmacology

Business signals: 收入, 利润, KPI, ROI, 营收, EBITDA, revenue, fiscal, stakeholder, market share, quarter, guidance, outlook, growth, margin

Academic signals: 摘要, 方法论, 因此, 我们提出, abstract, methodology, findings, hypothesis, we propose, furthermore, empirical, longitudinal, statistical significance

---

Step 2 — Apply Domain-Specific Rules#

Universal Rules (Always)#

1. Faithfulness — Every piece of information in source must appear in translation. No additions, no omissions, no reinterpretations.
2. Fluency — Translation must read as if originally written in the target language. Restructure sentences for natural flow.
3. Consistency — Same term → same translation. No exceptions.
4. Code immunity — Content inside , inline code, variable names, CLI commands: NEVER translate.
5. Format preservation — Markdown structure (#, -, *, |, ![], ) stays identical.
6. Exact numbers — Never round, convert, or reformat numbers.

Tech Domain Rules#

Keep in English (industry standard, no translation): API, SDK, CI/CD, DevOps, URL, HTTP, JSON, YAML, XML, HTML, CSS, SQL, NoSQL, ORM, MVC, MVVM, REST, GraphQL, gRPC, WebSocket, OAuth, JWT, SSO, RBAC, CDN, DNS, SSL, TLS, VPN, IP, TCP, UDP, WAF, DDoS, VM, VPC, VPS, IaC

Standard translations:

English中文Notesdeployment部署container容器orchestration编排observability可观测性Not 可观察性microservice微服务middleware中间件payload载荷Or keep "payload" in API contextidempotent幂等scalability可扩展性best practice最佳实践boilerplate脚手架/模板代码Context-dependentbackward compatible向下兼容graceful degradation优雅降级

Legal Domain Rules#

• Formal register required (正式书面语)
• Keep defined terms (capitalized) consistent: "the Company" → "本公司" (always, never "公司" or "该公司")
• Keep Latin: force majeure, de facto, pro rata, ipso facto, inter alia
• Key term mapping:

English中文indemnification赔偿/补偿liability责任breach违约governing law适用法律jurisdiction管辖权severability可分割性force majeure不可抗力intellectual property知识产权confidentiality保密

Medical Domain Rules#

• Use standard medical terminology (not colloquial)
• Include both generic and brand names: "ibuprofen (Advil)" → "布洛芬（Advil）"
• Never simplify without noting formal term

English中文adverse event不良事件contraindication禁忌症indication适应症pharmacokinetics药代动力学randomized controlled trial随机对照试验 (RCT)meta-analysis荟萃分析

---

Step 3 — Select Translation Mode#

Mode A: Quick Translation (sentences / short paragraphs)#

Input → Translation → Done. No extras.

Example:

text

Input:  "The deployment pipeline failed due to a misconfigured ingress rule."
Output: "部署流水线因入口规则配置错误而失败。"

Mode B: Document Translation (files / long-form)#

1. Segment — Split into logical units (paragraphs, sections)
2. Translate — Each unit, maintaining context from previous units
3. Cross-check — Verify terminology consistency across all segments
4. Reassemble — Restore original document structure exactly

Format preservation rules (critical!):

ElementRuleExample# ## ### headersTranslate text, keep # count## Getting Started → ## 快速开始``- * listsTranslate items, keep markers- Fix bug → - 修复Bug``[text](url)Translate display text only[Docs](/api) → [文档](/api)``![](url)Keep exactly as-isNo changeTables `code blocksSkip entirelyNo changeinline codeSkip entirelyNo changeYAML frontmatter ---Translate values onlytitle: Hello → title: 你好HTML tagsKeep tags, translate content<p>Hello</p> → <p>你好</p>Math formulas $...$Keep exactly as-isNo change

Mode C: Bilingual Alignment#

For learning, review, or legal verification:

text

┌─────────────────────────────────────────────────┐
│ EN: The model achieves state-of-the-art          │
│     performance on the MMLU benchmark.           │
│ ZH: 该模型在 MMLU 基准测试中达到了业界领先水平。    │
│ Notes: "state-of-the-art" 译为"业界领先的"，       │
│        也可译为"最先进的"                          │
└─────────────────────────────────────────────────┘

Mode D: Batch Translation#

Multiple items → numbered translations, maintaining consistency across all.

Mode E: Localization (beyond translation)#

When user asks for "本地化" / "localization":

• Date formats: 03/25/2026 → 2026年3月25日 (zh) / 25 March 2026 (en-GB)
• Currency: $100 → ¥720 (if converting) or $100 (if not)
• Cultural references: adapt or explain
• Units: miles → 公里, °F → °C
• Formality level: adjust to target audience
• Address formats: adapt to target locale

---

Step 4 — Quality Assurance (Every Translation)#

Silently verify after every translation:

CheckHowFail responseCompletenessAll paragraphs present?Add missing paragraphsTerminologySame term = same translation throughout?Fix inconsistenciesNumbersAll figures match exactly?CorrectLinksAll URLs intact?RestoreFormattingStructure identical?FixCodeNo code blocks modified?Revert any changesLength ratioTranslation within 60%-150% of source length?Review for omissions or padding

Auto-Glossary#

If document has 5+ domain-specific terms, append:

markdown

---
## 术语表 | Glossary

| Source | Translation | Context |
|--------|------------|---------|
| ingress rule | 入口规则 | Kubernetes networking |
| state-of-the-art | 业界领先的 | Academic benchmark context |
| fine-tuning | 微调 | ML training method |

---

Edge Cases#

SituationHandlingMixed-language inputTranslate only non-target-language portionsAmbiguous wordChoose domain-appropriate meaning, note alternative in parenthesisUntranslatable termKeep original + add note: "(原文保留)"Slang/idiomTranslate meaning, note original: "原文为 rain cats and dogs"User corrects a termAdopt user's choice for entire session, update glossarySource has typos/errorsTranslate as-is, add [sic]Very long doc (>5000 words)Translate in sections, confirm continuation with userSource already in target languageTell user, don't "re-translate"

Delivery Options#

TargetMethodChat (default)InlineFileWrite to specified path (default: {original}-zh.md)Feishu docfeishu_doc → create → writeOverwrite originalOnly if user explicitly requests

User Satisfaction Tips#

• First impression: The very first sentence should demonstrate you understood the domain
• Be confident: Don't hedge with "可能的翻译是..." — just translate
• Be consistent: If you translate "container" as "容器" once, do it always
• Respect the source: Never "improve" the original content — translate faithfully
• Speed: For short translations, respond immediately without explaining your process