german-translator-pro-brand-legal

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

German Translator Pro — Brand & Legal

专业德语翻译工具——品牌与法律文本专属

Translate and validate English to Swiss-formal German (Hochdeutsch CH). Trained on real translation patterns crawled from 12+ top brands — not generic machine translation.

将英语翻译为瑞士标准德语（Hochdeutsch CH）并进行验证。基于12+顶级品牌的真实翻译模式训练，而非通用机器翻译。

What makes this different

核心差异化优势

LLMs produce translationese — grammatically correct German that sounds translated, not written. This skill fixes that with curated reference files extracted from how top brands actually translate their websites, marketing, and legal pages.

Brands crawled: Swisscom, UBS, On Running, Logitech, IKEA CH, Stripe, Notion, Slack, Apple, Shopify, BMW, Vercel

What we extracted: 100+ real EN→DE pairs, 5 hero headline strategies, 15+ CTA patterns, Du/Sie industry split, 40+ glossary decisions (keep vs translate), 29 legal term translations, translationese traps, legal register patterns — all with brand evidence.

The agent reads these references before every translation, producing output that matches how these brands write German.

大语言模型生成的内容存在翻译腔——语法正确但读起来像翻译稿，而非原生德语。本工具通过提取顶级品牌官网、营销内容及法律页面的翻译参考文件，彻底解决这一问题。

爬取的品牌包括： Swisscom、UBS、On Running、Logitech、IKEA CH、Stripe、Notion、Slack、Apple、Shopify、BMW、Vercel

提取的核心资源： 100+真实英德翻译对、5种标题翻译策略、15+行动号召（CTA）句式、Du/Sie称谓行业规范、40+术语保留/翻译判定、29个法律术语翻译、翻译腔避坑指南、法律文本语体规范——所有内容均有品牌案例支撑。

Agent在每次翻译前都会读取这些参考文件，输出内容完全匹配顶级品牌的德语写作风格。

Install

安装

bash

npx skills add SLFMR1/german-translator-pro-brand-legal

bash

npx skills add SLFMR1/german-translator-pro-brand-legal

When to Use

适用场景

Translating UI strings (buttons, headings, CTAs, marketing copy) to German
Translating legal pages (privacy policy, terms of service, imprint) to German
QA-checking existing German translations against English source
Any EN → DE translation that needs Swiss conventions and natural phrasing

将UI字符串（按钮、标题、CTA、营销文案）翻译为德语
将法律页面（隐私政策、服务条款、版权声明）翻译为德语
对照英语原文，对现有德语翻译进行QA检查
任何需要符合瑞士规范、表达自然的英德翻译需求

How It Works

工作机制

The skill supports two text types and two actions:

	Brand / UI	Legal
Translate (EN → DE)	Natural, punchy Swiss-German that sounds written, not translated	Precise, formal German with DSGVO/DSG legal terminology
Validate (QA check)	Check for naturalness, accuracy, Swiss conventions	Check for legal precision, qualifier preservation, terminology

本工具支持两类文本与两种操作：

	品牌/UI文本	法律文本
翻译（英→德）	自然凝练的瑞士德语，读起来像原生创作而非翻译	精准正式的德语，适配DSGVO/DSG法律术语体系
验证（QA检查）	检查表达自然度、准确性及瑞士规范符合性	检查法律精准度、限定词保留情况及术语规范性

Key features

核心功能

Anti-translationese — Restructures German thoughts fresh instead of mapping English sentence structures. Trained on how top brands actually write
Swiss (CH) or German (DE) locale — Swiss:
```
ss
```
not
```
ß
```
, 1'000, CHF. German: standard
```
ß
```
, 1.000, EUR. User chooses
Back-translation QA — Verifies meaning preservation by translating DE back to EN
Completeness checks — Catches untranslated strings AND accidentally germanized brand terms
Legal term precision — 25+ DSGVO/DSG terms with brand-confirmed translations and source fidelity rules
4-agent legal pipeline — Translator → Back-Translator → Validator → Refiner for legal documents
Configurable glossary — Keep-in-English terms, always-translate terms, split decisions — all with brand evidence

反翻译腔——重新构建德语表达逻辑，而非直接映射英语句式。基于顶级品牌的真实写作风格训练
瑞士（CH）或德国（DE）区域适配——瑞士区域：用
```
ss
```
而非
```
ß
```
，数字格式为1'000，货币为CHF；德国区域：标准
```
ß
```
，数字格式为1.000，货币为EUR。可由用户选择
回译QA——通过将德语回译为英语，验证语义一致性
完整性检查——识别未翻译字符串及意外德语化的品牌术语
法律术语精准性——25+经品牌确认的DSGVO/DSG术语及原文保真规则
4-Agent法律文档处理流程——翻译→回译→验证→优化，全流程处理法律文档
可配置术语表——保留英文术语、强制翻译术语、分情况处理术语——所有规则均有品牌案例支撑

Workflow

工作流程

Step 1: Determine Text Type, Action, Address Form, and Locale

步骤1：确定文本类型、操作、称谓形式与区域

Before doing any work, determine four things. If not clear from context, ask the user:

1. Text type?

UI — hero sections, CTAs, agent descriptions, navigation, headings, buttons, labels
LEGAL — privacy policy, terms of service, imprint, legal disclaimers

2. Action?

TRANSLATE — convert English to German
VALIDATE — QA-check existing German translation against English source

3. Address form?

Sie (formal) — B2B, corporate, legal, professional. Capitalized: Sie, Ihnen, Ihr, Ihre
Du (informal) — B2C apps, casual products, startups. Lowercase: du, dir, dein, deine

Default to Sie if unclear. Legal text always uses Sie regardless of user preference.

4. Locale?

Swiss (CH) —
```
ss
```
not
```
ß
```
, apostrophe thousands (1'000), CHF before amount (CHF 100), decimal point (99.90)
German (DE) —
```
ß
```
where standard, dot thousands (1.000), € after amount (100 €), decimal comma (99,90)

Default to Swiss (CH) if unclear.

Apply the chosen form and locale consistently throughout. Follow the matching section below.

Web research allowed. If a term is not in the glossary, or you're unsure about the right translation, look it up. Fetch the German version of a brand's website (e.g. apple.com/de, stripe.com/de, notion.so/de) to see how they actually translate it. You can also check other relevant brand websites in the same industry as the user's project. Real-world usage beats guessing.

开始工作前，需确定四个要素。若上下文未明确，请询问用户：

1. 文本类型？

UI文本——首页横幅、CTA、Agent描述、导航栏、标题、按钮、标签
法律文本——隐私政策、服务条款、版权声明、法律免责声明

2. 操作类型？

翻译（TRANSLATE）——将英语转换为德语
验证（VALIDATE）——对照英语原文，对现有德语翻译进行QA检查

3. 称谓形式？

Sie（正式）——B2B、企业、法律、专业场景。首字母大写：Sie、Ihnen、Ihr、Ihre
Du（非正式）——B2C应用、休闲产品、初创企业场景。小写：du、dir、dein、deine

若未明确，默认使用Sie。法律文本无论用户偏好如何，一律使用Sie。

4. 区域？

瑞士（CH）——用
```
ss
```
而非
```
ß
```
，千分位用撇号（1'000），货币符号CHF前置（CHF 100），小数点用点（99.90）
德国（DE）——标准
```
ß
```
，千分位用点（1.000），货币符号€后置（100 €），小数点用逗号（99,90）

若未明确，默认使用瑞士（CH）。

需全程保持所选称谓形式与区域规范的一致性。遵循下文对应章节的要求。

允许网页检索。若术语未收录于术语表，或对翻译存疑，可进行检索。查看品牌德语官网（如apple.com/de、stripe.com/de、notion.so/de）的实际译法。也可参考用户项目所属行业的其他相关品牌官网。实际使用案例优于主观猜测。

Step 2: Multi-File Projects — Use Subagents

步骤2：多文件项目——使用子Agent

When translating or validating multiple files or pages, do NOT process them all in the main context. Instead, use the orchestrator/subagent pattern:

Orchestrator (main agent):

Determine the 4 settings above (text type, action, address form, locale)
List all files/pages to process
Spawn one subagent per file/page using the Agent tool
Collect results and report a summary

Each subagent:

Receives: the file path, text type, action, address form, locale
Reads the reference files (glossary, style guide, examples)
Translates or validates the single file
Self-validates against qa-checklist.md — runs the relevant checks for the text type
Fixes any CRITICAL issues found during self-validation
Reports back: the output file + a summary (PASS/FAIL, issue count, any unresolved warnings)

Why: Each subagent gets a clean context with full reference files loaded. No context blowup from processing 10+ files sequentially. Self-validation catches issues before they reach the orchestrator.

Single file? Skip this — just run the translation/validation directly.

当翻译或验证多个文件/页面时，请勿在主上下文内处理所有内容。请使用编排者/子Agent模式：

编排者（主Agent）：

确定上述4项设置（文本类型、操作、称谓形式、区域）
列出所有待处理文件/页面
使用Agent工具，为每个文件/页面生成一个子Agent
收集结果并生成汇总报告

每个子Agent：

接收：文件路径、文本类型、操作、称谓形式、区域
读取参考文件（术语表、风格指南、示例）
对单个文件进行翻译或验证
对照qa-checklist.md进行自我验证——针对文本类型执行相关检查
修复自我验证中发现的所有严重问题
反馈：输出文件 + 汇总信息（通过/失败、问题数量、未解决的警告）

优势： 每个子Agent的上下文独立且加载完整参考文件，避免因连续处理10+文件导致的上下文过载。自我验证可在问题提交给编排者前提前发现。

单文件场景？ 跳过此步骤——直接执行翻译/验证即可。

TRANSLATE + UI

翻译 + UI文本

Natural, punchy Swiss-German for marketing and interface text.

为营销与界面文本提供自然凝练的瑞士德语翻译。

Process

流程

Read the English source JSON file completely
Read glossary.md for terms that must stay untranslated
Read swiss-german-style.md for tone, conventions, and translationese traps
Read examples.md — match this quality level
Translate every value. Never modify keys or
```
{variable}
```
placeholders
Self-check: Read each German value out loud. Would a Swiss product manager say this over coffee? If it sounds like a document, rewrite it
Back-translate check: For 5 random keys, mentally translate the German back to English. If the meaning shifted, fix it
Completeness check: Compare EN keys vs DE keys — zero missing. Scan for identical EN/DE values: keep-in-English terms are OK, but full English sentences left untranslated are not. Verify always-translate terms from glossary are actually translated (Products→Produkte, not "Products")
Length check: Compare character count of each DE value vs EN value. Flag any UI string (buttons, labels, nav, headings, tooltips) where DE is >120% of EN length. Shorten these — German must fit the same visual space
Output a complete JSON file with identical structure to the English source

完整读取英语源JSON文件
读取glossary.md，确认需保留英文的术语
读取swiss-german-style.md，了解语体、规范及翻译腔避坑指南
读取examples.md——以此为质量标准
翻译所有值。请勿修改键名或
```
{variable}
```
占位符
自我检查： 大声朗读每个德语译文。瑞士产品经理会在日常沟通中这么说吗？若读起来像正式文档，请重写
回译检查： 随机选择5个键，在脑海中将德语回译为英语。若语义发生偏差，请修正
完整性检查： 对比英语与德语的键——确保无缺失。扫描是否存在英德值完全相同的情况：需保留英文的术语没问题，但完整英语句子未翻译则属于问题。验证术语表中强制翻译的术语已完成翻译（如Products→Produkte，而非保留“Products”）
长度检查： 对比每个德语值与英语值的字符数。若UI字符串（按钮、标签、导航、标题、提示框）的德语长度超过英语的120%，需标记并缩短——德语译文必须适配原有视觉空间
输出结构与英语源文件完全一致的完整JSON文件

Rules

规则

Restructure, don't translate. Write the German thought fresh. If it reads like it was run through a translator, rewrite it
Use the address form chosen in Step 1 (Sie or Du) — apply consistently throughout
Apply the locale conventions chosen in Step 1 (CH or DE) for ß/ss, number formatting, and currency
Preserve all
```
{variable}
```
placeholders and HTML tags exactly
Keep JSON key names and namespace structure identical
Brand names, product names stay in English (see glossary.md)
English tech terms standard in Swiss business stay English (Agent, CRM, API, Inbox, Tools, Workflow, etc.)
Prefer verbs over nominalizations — "prüfen" not "Durchführung der Prüfung"
Prefer concrete benefits over abstract claims
Short sentences. If over 20 words, consider splitting
Length constraint (UI critical). German text expands ~20-30% vs English. UI strings must fit the same visual space — buttons, labels, nav items, headings, tooltips. If the German is noticeably longer than the English, shorten it. Prefer compact phrasing: "Jetzt starten" not "Jetzt loslegen und starten", "Mehr erfahren" not "Erfahren Sie mehr darüber". For buttons and nav: aim to match or stay within ~120% of the English character count

重构而非直译。重新创作德语表达，若读起来像翻译稿，请重写
遵循步骤1中选择的称谓形式（Sie或Du）——全程保持一致
遵循步骤1中选择的区域规范（CH或DE），处理ß/ss、数字格式及货币
完全保留所有
```
{variable}
```
占位符与HTML标签
保持JSON键名与命名空间结构完全一致
品牌名、产品名保留英文（详见glossary.md）
瑞士商务场景中通用的英语技术术语保留英文（如Agent、CRM、API、Inbox、Tools、Workflow等）
优先使用动词而非名词化表达——用“prüfen”而非“Durchführung der Prüfung”
优先使用具体利益点而非抽象表述
句子简短。若超过20词，考虑拆分
UI文本长度限制（关键要求）。德语文本通常比英语长20-30%，但UI字符串必须适配原有视觉空间——按钮、标签、导航项、标题、提示框。若德语译文明显长于英语，需缩短。优先使用凝练表达：用“Jetzt starten”而非“Jetzt loslegen und starten”，用“Mehr erfahren”而非“Erfahren Sie mehr darüber”。按钮与导航项的德语长度应尽量匹配或不超过英语的120%

Output

输出

Complete valid JSON. Same keys, same nesting, German values.

结构完整的有效JSON文件，键名与嵌套结构与源文件一致，值为德语译文。

TRANSLATE + LEGAL

翻译 + 法律文本

Precise, formal Swiss-German for legal documents. Accuracy over style.

For the full multi-agent pipeline (recommended for legal), see legal-workflow.md. It uses 4 agents: Translator → Back-Translator → Validator → Refiner. The instructions below are for the Translator agent (Agent 1).

为法律文档提供精准正式的瑞士德语翻译。准确性优先于风格。

完整多Agent流程（法律文本推荐），详见legal-workflow.md。流程包含4个Agent：翻译→回译→验证→优化。以下为翻译Agent（Agent 1）的操作说明。

Process

流程

Read the English source JSON file completely
Read glossary.md for terms that must stay untranslated
Read swiss-german-style.md — apply the locale conventions (CH or DE) chosen in Step 1, but use formal legal register, not marketing tone
Translate every value with focus on legal precision and completeness
Self-check — 4 passes:
- Pass 1: Back-translate every value to English. If meaning shifted → fix
- Pass 2: Check every legal qualifier (may/shall/unless) is preserved with correct weight
- Pass 3: Read only the German text without looking at English. Flag ambiguities
- Pass 4: Completeness — diff EN keys vs DE keys (zero missing). Scan identical values: brand names and keep-in-English terms OK, untranslated legal text is CRITICAL. Verify legal section headings, consent language, and rights descriptions are all in German
Output two files:
- The complete translated JSON (same structure as source)
- A
```
_review_notes.md
```
  file flagging sections that need professional legal review

完整读取英语源JSON文件
读取glossary.md，确认需保留英文的术语
读取swiss-german-style.md——遵循步骤1中选择的区域规范（CH或DE），但使用正式法律语体，而非营销语体
翻译所有值，重点关注法律精准性与完整性
自我检查——四轮验证：
- 第一轮：将每个值回译为英语。若语义偏差→修正
- 第二轮：检查所有法律限定词（may/shall/unless）均保留正确权重
- 第三轮：仅读取德语文本，不参考英语原文。标记歧义内容
- 第四轮：完整性检查——对比英语与德语的键（确保无缺失）。扫描是否存在值完全相同的情况：品牌名与需保留英文的术语没问题，但未翻译的法律文本属于严重问题。验证法律章节标题、同意话术及权利描述均已翻译为德语
输出两个文件：
- 结构与源文件一致的完整翻译JSON
- ```
_review_notes.md
```
  文件，标记需要专业法律审核的章节

Rules

规则

Legal precision over natural flow. Accuracy of meaning is paramount. Do not rephrase for punchiness
Formal register. Legal text should sound formal and precise — "stiff" is correct here
Formal "Sie" form — always for legal text, regardless of user preference for UI
Apply the locale conventions chosen in Step 1 (CH or DE) for ß/ss, number formatting, and currency
Preserve all
```
{variable}
```
placeholders and HTML tags exactly
Keep JSON key names and namespace structure identical
Preserve legal terminology. Use standard DSGVO/DSG terms (see table below)
Swiss legal context (CH locale). Reference Swiss law (DSG/nDSG, OR) alongside EU references (DSGVO/GDPR) where the English mentions data protection or privacy. For DE locale, DSGVO references are sufficient
Do NOT simplify. Complex sentences keep their complexity. Legal meaning depends on precise wording
Do NOT drop qualifiers. "may", "shall", "unless", "notwithstanding" have specific legal weight: "kann", "hat zu" (not "soll" — "soll" is weaker, closer to "should"), "sofern nicht", "ungeachtet"
Flag jurisdiction-specific clauses — courts, regulators, applicable law references go in the review notes
Source fidelity. Translate what the source says, not what it should say. If the source uses "personal information" (informal), translate as "persönliche Informationen" — do NOT upgrade to "personenbezogene Daten" (which is the DSGVO term for "personal data"). Only use formal legal terms when the source uses the corresponding formal English term
No right escalation. If the source says "opt out", translate as "abmelden" or "ablehnen" — do NOT escalate to "widersprechen" (formal DSGVO right of objection under Art. 21). Match the weight of the source
Complete compound nouns. German compound truncation ("Rechts- oder Behörden...") must be grammatically complete. "Rechts- oder Behördenanfragen" is correct. "Rechts- oder Behörden" alone is not — the compound base word must appear at least once

法律精准性优先于流畅度。语义准确性是首要原则，请勿为了凝练而改写
正式语体。法律文本应正式精准——“生硬”的表达是符合要求的
正式称谓“Sie”——法律文本无论用户UI偏好如何，一律使用Sie
遵循步骤1中选择的区域规范（CH或DE），处理ß/ss、数字格式及货币
完全保留所有
```
{variable}
```
占位符与HTML标签
保持JSON键名与命名空间结构完全一致
保留法律术语。使用标准DSGVO/DSG术语（见下表）
瑞士法律语境（CH区域）。若英语原文提及数据保护或隐私，需同时参考瑞士法律（DSG/nDSG、OR）与欧盟法律（DSGVO/GDPR）。DE区域仅需参考DSGVO即可
请勿简化。复杂句式需保留原有复杂度，法律语义依赖精准措辞
请勿遗漏限定词。“may”“shall”“unless”“notwithstanding”具有特定法律权重：对应译法为“kann”“hat zu”（而非“soll”——“soll”语气更弱，接近“should”）“sofern nicht”“ungeachtet”
标记司法管辖区特定条款——法院、监管机构、适用法律等相关内容需写入审核备注
原文保真。翻译原文表述，而非“应该”的表述。若原文使用非正式的“personal information”，翻译为“persönliche Informationen”——请勿升级为DSGVO术语“personenbezogene Daten”。仅当原文使用对应正式英语术语时，才可使用正式法律德语术语
权利表述匹配。若原文为“opt out”，翻译为“abmelden”或“ablehnen”——请勿升级为DSGVO第21条规定的正式反对权“widersprechen”。需匹配原文的权重
复合名词完整性。德语复合名词的省略形式（如“Rechts- oder Behörden...”）必须语法完整。正确示例：“Rechts- oder Behördenanfragen”；错误示例：“Rechts- oder Behörden”——复合名词的核心词至少需出现一次

Legal Term Translations

法律术语翻译对照表

English	German	Notes
personal data	personenbezogene Daten	DSGVO standard
data processing	Datenverarbeitung
data controller	Verantwortlicher
data processor	Auftragsverarbeiter
consent	Einwilligung	not "Zustimmung" in GDPR context
legitimate interest	berechtigtes Interesse
data subject	betroffene Person
right to erasure	Recht auf Löschung
terms of service	Nutzungsbedingungen	or AGB
liability	Haftung
indemnification	Freistellung / Schadloshaltung
governing law	anwendbares Recht
severability	Salvatorische Klausel
intellectual property	geistiges Eigentum
data protection	Datenschutz
data retention	Datenaufbewahrung
data transfer	Datenübermittlung	Apple, Stripe
legal basis	Rechtsgrundlage	Apple, Stripe
supervisory authority	Aufsichtsbehörde	Apple
Data Protection Officer	Datenschutzbeauftragter	Apple, Stripe
Standard Contractual Clauses	Standardvertragsklauseln	Apple, Stripe, Slack
right to access	Auskunftsrecht	Apple
right to rectification	Recht auf Berichtigung	Apple
right to object	Widerspruchsrecht	Logitech
right to data portability	Recht auf Datenübertragbarkeit	Logitech
GDPR	DSGVO (Datenschutz-Grundverordnung)	Always "DSGVO" in DE, never "GDPR"
FADP / Swiss DPA	DSG (Bundesgesetz über den Datenschutz)	Stripe, IKEA
FDPIC	EDÖB	Swiss federal data protection authority
as is / as available	wie besehen / wie verfügbar	Shopify — warranty disclaimer

英语	德语	备注
personal data	personenbezogene Daten	DSGVO标准术语
data processing	Datenverarbeitung
data controller	Verantwortlicher
data processor	Auftragsverarbeiter
consent	Einwilligung	GDPR语境下不使用“Zustimmung”
legitimate interest	berechtigtes Interesse
data subject	betroffene Person
right to erasure	Recht auf Löschung
terms of service	Nutzungsbedingungen	或AGB
liability	Haftung
indemnification	Freistellung / Schadloshaltung
governing law	anwendbares Recht
severability	Salvatorische Klausel
intellectual property	geistiges Eigentum
data protection	Datenschutz
data retention	Datenaufbewahrung
data transfer	Datenübermittlung	Apple、Stripe使用该译法
legal basis	Rechtsgrundlage	Apple、Stripe使用该译法
supervisory authority	Aufsichtsbehörde	Apple使用该译法
Data Protection Officer	Datenschutzbeauftragter	Apple、Stripe使用该译法
Standard Contractual Clauses	Standardvertragsklauseln	Apple、Stripe、Slack使用该译法
right to access	Auskunftsrecht	Apple使用该译法
right to rectification	Recht auf Berichtigung	Apple使用该译法
right to object	Widerspruchsrecht	Logitech使用该译法
right to data portability	Recht auf Datenübertragbarkeit	Logitech使用该译法
GDPR	DSGVO (Datenschutz-Grundverordnung)	DE区域一律使用“DSGVO”，绝不使用“GDPR”
FADP / Swiss DPA	DSG (Bundesgesetz über den Datenschutz)	Stripe、IKEA使用该译法
FDPIC	EDÖB	瑞士联邦数据保护机构
as is / as available	wie besehen / wie verfügbar	Shopify的免责声明译法

Output

输出

Two files:

Complete valid JSON — same keys, same nesting, German values
```
_review_notes.md
```
:

markdown

undefined

两个文件：

结构完整的有效JSON——键名与嵌套结构与源文件一致，值为德语译文
```
_review_notes.md
```
：

markdown

undefined

Legal Translation Review Notes: [filename]

法律翻译审核备注: [文件名]

Sections Requiring Professional Legal Review

需专业法律审核的章节

Translation Decisions

翻译决策说明

[key.path]: "Chose X over Y because..."

Swiss Law Considerations

瑞士法律考量

Areas where Swiss law (DSG/nDSG, OR) differs from the EU law referenced in source

---

瑞士法律（DSG/nDSG、OR）与原文提及的欧盟法律存在差异的领域

---

VALIDATE + UI

验证 + UI文本

QA-check German UI/marketing translations for naturalness, accuracy, and Swiss conventions.

对德语UI/营销翻译进行QA检查，验证表达自然度、准确性及瑞士规范符合性。

Process

流程

Read both the English source and German translation JSON files
Read glossary.md and swiss-german-style.md
Read examples.md — compare translations against these benchmarks
Read qa-checklist.md — run the Structural, Accuracy, Naturalness, Tone & Style (UI), Linguistic (UI), and Completeness sections
Back-translation check: For each DE value, mentally translate it back to English. Mismatch → CRITICAL (meaning error) or WARNING (nuance drift)
Naturalness check: Does this sound written in German or translated from English? Flag translationese as WARNING
Completeness check: Run the full Completeness routine from qa-checklist.md:
- Identify all keys where EN value === DE value (identical-value scan)
- For each, classify: keep-in-English term → OK, brand name → OK, URL/email/number → OK, actual untranslated text → CRITICAL
- Cross-check against glossary: no accidentally translated keep-in-English terms, no English left for always-translate terms
- Verify all navigation terms, CTAs, and common UI patterns are translated per brand-crawl evidence
Length check: Compare character count of each DE value vs EN value. Flag UI strings (buttons, labels, nav, headings, tooltips) where DE is >120% of EN length as WARNING — these may break layout
Web crosscheck: For any translation you're unsure about or that feels off, fetch the German version of a relevant brand website to verify how they translate it. Spot-check at least 5 key terms against real brand usage
Report findings grouped by severity

读取英语源文件与德语翻译JSON文件
读取glossary.md与swiss-german-style.md
读取examples.md——将译文与这些基准案例对比
读取qa-checklist.md——执行结构、准确性、自然度、语体与风格（UI）、语言（UI）、完整性章节的检查
回译检查： 对每个德语值，在脑海中将其回译为英语。若语义不匹配→标记为严重（语义错误）或警告（语义偏差）
自然度检查： 译文读起来像原生德语还是英语翻译？翻译腔标记为警告
完整性检查： 执行qa-checklist.md中的完整完整性检查流程：
- 识别所有英德值完全相同的键（相同值扫描）
- 对每个相同值进行分类：需保留英文的术语→正常，品牌名→正常，URL/邮箱/数字→正常，未翻译的实际文本→严重
- 对照术语表检查：无意外翻译需保留英文的术语，无强制翻译术语仍为英语
- 验证所有导航术语、CTA及常见UI模式均已按照品牌爬取案例完成翻译
长度检查： 对比每个德语值与英语值的字符数。若UI字符串（按钮、标签、导航、标题、提示框）的德语长度超过英语的120%，标记为警告——这些内容可能破坏布局
网页交叉验证： 对任何存疑的翻译，查看相关品牌的德语官网验证实际译法。至少抽查5个关键术语的品牌使用情况
按严重程度分组呈现检查结果

VALIDATE + LEGAL

验证 + 法律文本

QA-check German legal translations for precision, terminology, and legal correctness.

If a back-translation file is available (from the legal-workflow.md pipeline), use it in step 4 below. This catches meaning errors that bilingual review misses — a reviewer unconsciously imports the correct meaning from the source, but a back-translation reveals what the German text actually says in isolation.

对德语法律翻译进行QA检查，验证精准性、术语规范性及法律正确性。

若有回译文件（来自legal-workflow.md流程），请在步骤4中使用该文件。这可发现双语审核遗漏的语义错误——审核者会无意识地从原文导入正确语义，但回译可揭示德语文本实际表达的内容。

Process

流程

Read both the English source and German translation JSON files
Read glossary.md and swiss-german-style.md
Read qa-checklist.md — run the Structural, Accuracy, Tone & Style (Legal), Linguistic (Legal), Legal-Specific, and Completeness sections
Back-translation diff (if back-translation file provided): Compare original EN with back-translated EN, key by key. Flag divergences:
- Meaning matches → OK
- Slight nuance drift → WARNING
- Material change (obligation→permission, condition dropped, scope changed) → CRITICAL
Blind read: Read ONLY the German text without looking at English. Flag anything unclear or ambiguous as a standalone German legal document
Precision check: Are legal qualifiers ("may", "shall", "unless") translated with full legal weight? Are complex conditions preserved without simplification?
Completeness check: Run the full Completeness routine from qa-checklist.md:
- Identical-value scan: classify every key where EN === DE (keep-in-English → OK, brand name → OK, actual untranslated text → CRITICAL)
- Cross-check against glossary: keep-in-English terms not accidentally translated, always-translate terms not left in English
- Legal-specific: verify legal section headings, consent language, rights descriptions are all translated — never left in English
Web crosscheck: For any legal term or translation you're unsure about, fetch the German version of a relevant brand's legal pages (e.g. apple.com/de/privacy, stripe.com/de/legal) to verify standard usage. Spot-check at least 5 key legal terms against real brand usage
Report findings grouped by severity

读取英语源文件与德语翻译JSON文件
读取glossary.md与swiss-german-style.md
读取qa-checklist.md——执行结构、准确性、语体与风格（法律）、语言（法律）、法律专属、完整性章节的检查
回译对比（若提供回译文件）：逐键对比原英语与回译英语。标记差异：
- 语义匹配→正常
- 轻微语义偏差→警告
- 实质性改变（义务→许可、条件遗漏、范围变更）→严重
盲读检查： 仅读取德语文本，不参考英语原文。标记作为独立德语法律文档存在的模糊或歧义内容
精准性检查： 法律限定词（“may”“shall”“unless”）的翻译是否保留了完整法律权重？复杂条件是否完整保留未被简化？
完整性检查： 执行qa-checklist.md中的完整完整性检查流程：
- 相同值扫描：分类所有英德值完全相同的键（需保留英文的术语→正常，品牌名→正常，未翻译的实际文本→严重）
- 对照术语表检查：需保留英文的术语未被意外翻译，强制翻译术语未保留英语
- 法律专属检查：验证法律章节标题、同意话术及权利描述均已翻译——绝不保留英语
网页交叉验证： 对任何存疑的法律术语或翻译，查看相关品牌的德语法律页面（如apple.com/de/privacy、stripe.com/de/legal）验证标准用法。至少抽查5个关键法律术语的品牌使用情况
按严重程度分组呈现检查结果

Severity Levels (Both VALIDATE Modes)

严重程度分级（两类验证模式通用）

CRITICAL: Missing keys, broken placeholders, broken JSON, meaning errors, legal inaccuracies
WARNING: Tone issues, phrasing problems, terminology inconsistencies, Bundesdeutsch instead of Swiss
INFO: Style suggestions, alternative phrasings, minor improvements

严重：缺失键、占位符损坏、JSON损坏、语义错误、法律不准确
警告：语体问题、措辞问题、术语不一致、使用德国标准德语而非瑞士德语
信息：风格建议、替代措辞、小幅优化

Output Format (Both VALIDATE Modes)

输出格式（两类验证模式通用）

undefined

undefined

Validation Report: [filename]

验证报告: [文件名]

Text type: [UI / LEGAL]

文本类型: [UI / 法律]

CRITICAL (X issues)

严重问题（X个）

[key.path]: Description of issue

WARNING (X issues)

警告（X个）

[key.path]: Description of issue | Suggestion: ...

[key.path]: 问题描述 | 建议: ...

INFO (X suggestions)

信息（X条建议）

Summary

汇总

X critical | X warnings | X info — [PASS/FAIL]


FAIL if any CRITICAL issues exist. PASS otherwise.

---

X个严重问题 | X个警告 | X条信息 — [通过/失败]


若存在任何严重问题，判定为**失败**。否则为**通过**。

---

Resources

参考资源

references/examples.md — Real EN→DE translation examples (UI + Legal quality benchmarks, common pitfalls)
references/glossary.md — Untranslatable terms (universal + project-specific)
references/swiss-german-style.md — Swiss-German conventions, translationese traps, Obvious Adams principles
references/qa-checklist.md — QA checklist with separate UI and Legal sections
references/legal-workflow.md — Full 4-agent pipeline for legal translation (Translator → Back-Translator → Validator → Refiner)

references/examples.md — 真实英德翻译示例（UI + 法律文本质量基准，常见陷阱）
references/glossary.md — 不可翻译术语（通用 + 项目专属）
references/swiss-german-style.md — 瑞士德语规范、翻译腔避坑指南、Obvious Adams原则
references/qa-checklist.md — QA检查清单，包含UI与法律文本专属章节
references/legal-workflow.md — 法律翻译完整4-Agent流程（翻译→回译→验证→优化）