Translate

This skill provides guidelines for accurate, fluent translation, with agent-based parallel processing for large files and multi-file batches.

On Translation

Translation is writing across languages — rendering content expressed in one language into another, minimizing the gap between them.

Good translation goes beyond conveying information accurately. It re-expresses that information in language that is beautiful and natural, capturing the spirit of the original author. When readers encounter the translation, they should feel the piece was written in their language from the start — not carried over from a foreign one. Through parallel processing, this standard is maintained even for long texts and multi-file batches.

Core anchor: Translation is writing — not conversion, but re-expression.

Core Principles

Imagination brings something into presence; translation gives what has come into presence a voice in another language.

The Nature of Translation: Reconstruct → Negotiate → Write

Translation is not word-for-word conversion. It is a three-step process:

Step 1: Reconstruct — Build the Imaginative Space

After reading the source text, construct a complete "imaginative space" in your mind. Different types of text generate fundamentally different spaces:

• Fiction → a world of characters, scenes, and emotions that you inhabit
• Technical documentation → an expert explaining to a student, and you are listening in
• Academic paper → a rigorous argument unfolding, and you are tracking the chain of reasoning
• Blog post → a friend talking to you, sharing experience and insight
• Product copy → someone demonstrating the value of something to you

This is not simply "understanding the text" — it is immersion. It means letting the intentional content of the source text manifest in consciousness (Husserl's eidetic intuition), letting absent scenes become present in the mind (Sartre's theory of imagination), and entering the text to grasp its flowing totality (Bergson's intuition). The quality of this imaginative space sets the ceiling for the translation.

The output of reconstruction does not stay at the level of "feeling" — it must be crystallized into the "translation tone" field of the translation brief: surface features such as person and register, and deeper features such as emotional register, narrative rhythm, lexical preferences, signature expressions, the movement of thought, and a sketch of the original "voice." These fields serve as the style baseline for all subsequent translation and sub-agent alignment.

Step 2: Negotiate — Enter into Dialogue with the Source

Once inside the imaginative space, you are not a passive observer but an interlocutor who can "question the author":

• What is this word actually trying to express in this context?
• What is the closest way for my readers to understand this concept?
• Is the author's tone here serious or ironic?
• Does this metaphor have an equivalent in the target language's world?

This step is the "negotiation" phase of translation — where the translator exercises judgment and brings their own interpretive subjectivity to bear on the source. The glossary fixes unified renderings for key terms; the translation brief captures critical decisions. The more thorough the negotiation, the more fluent the writing that follows.

Step 3: Write — Compose in the Target Language (executed by sub-agents)

Writing is the ceiling of translation — when comprehension is sound and negotiation is thorough, all remaining quality differences come down to craft. The primary agent does not execute writing directly in this step; its role is to ensure the translation brief provides sub-agents with a sufficient style baseline. The five dimensions of writing (precision, rhythm, register, naturalness, locale) and their specific requirements are detailed in the "Five Elements of Writing" section of references/subagent-prompt.md.

Strategy Must Be Adaptive

Hard-coded rules cannot cover every scenario. The same "rule" may be exactly inverted across different text types:

• Passive voice: eliminate in technical docs → standard practice in academic papers
• Rhetorical devices: avoid in technical docs → essential in literary works
• Domestication vs. foreignization: user manuals favor domestication → cultural texts may call for strategic foreignization
• Cognitive load: minimize aggressively in technical docs → literary works may legitimately challenge the reader
• Linguistic economy: pursue maximum concision in technical docs → prose may require elaboration and texture
• Regional vocabulary: mainland China uses "软件、程序、网络" → Taiwan uses "軟體、程式、網路" → Hong Kong is more heavily influenced by Cantonese

Accordingly, writing craft (precision, rhythm, register, naturalness), translation techniques (domestication/foreignization, cognitive load management, long-sentence restructuring), and locale positioning (the target region's lexical system and expressive conventions) are not treated as fixed rules. They are strategic dimensions that are adaptively determined in Phase 1 based on the characteristics of the source text and the target audience. Phase 1 produces two temporary files: a glossary (_glossary.md) to standardize renderings of core terms, and a translation brief (_translation_brief.md) to capture text type, translation tone, target locale, key challenges, and targeted strategies.

Translation Workflow

Path Conventions

SKILL_DIR = the directory containing this skill (the path following "Base directory for this skill:" in the system prompt).

Phase 0: Input Analysis

This skill handles Markdown and plain text. Other formats (web pages, PDFs, Word documents, images, etc.) must be converted to Markdown before invoking this skill.

Language detection: Source language is detected automatically. The default target language is Chinese (zh-CN); the user may specify a different target language or locale.

Scale assessment and strategy:

Decision logic:

• Single file ≤ 1000 lines → proceed immediately, no user confirmation needed
• Single file > 1000 lines or multiple files → report the plan to the user (file count, total line count, translation strategy) and wait for confirmation before proceeding

Phase 1: Read-Through and Preparation

This is the foundation of translation quality. The full text must be understood before any translation begins.

1. Read through the full text: Understand the topic, argument structure, and writing style to form a holistic impression.

2. Load user-persisted files (paths relative to SKILL_DIR; must be loaded using the Read tool):

   • {SKILL_DIR}/references/user-glossary.md — the user's accumulated domain glossary
   • {SKILL_DIR}/references/user-samples.md — the user's preferred translation style samples
   • Load each file if it exists; skip without error if it does not (these files accumulate gradually over time).

3. Extract the glossary (write to temporary _glossary.md):

   • Ground primarily in your read-through understanding, with user-glossary.md as a supplementary reference.
   • From user-glossary.md, import only entries relevant to the current document's domain; ignore unrelated domain terminology.
   • Extract new terms from the current document and merge with the filtered user-accumulated entries.
   • Three sections: terms to preserve as-is, standardized renderings, polysemous term handling.

4. Generate the translation brief (following the template at {SKILL_DIR}/references/translation-brief-template.md; write to temporary _translation_brief.md):

   • Text type: Technical documentation / Academic paper / Blog / Tutorial / Product copy / Other
   • Translation tone: Surface features (person, formality, tense preference) + deep features (emotional register, narrative rhythm, lexical preferences, signature expressions, the movement of thought, a sketch of the original "voice")
   • Language pair: Source language (auto-detected) → target language (default: Chinese)
   • Target locale: Determine the locale (default: zh-CN), which governs lexical choices, terminology, and expressive conventions. Regional differences are documented in references/locale-styles.md.
   • Reader profile: Who the translation is for, which affects vocabulary and depth of expression
   • Key translation challenges: Difficulties specific to this text
   • Targeted strategies: Concrete approaches for the challenges identified above
   • Cross-file consistency (multi-file scenarios): Shared glossary, shared brief, cross-file linkage

     ⚠️ Steps 2–4 must be executed regardless of file size. For small files, the output can be brief — but it cannot be skipped. The purpose of the temporary files is to make translation decisions auditable and to give sub-agents an inheritable style baseline. _glossary.md and _translation_brief.md are created in the source file's directory.

5. Split large files (if required):

   python {SKILL_DIR}/scripts/split_md.py {source_file} --max-lines 600 --output-dir {source_dir}/_parts/
   

   The script automatically generates: _part_NN.md (segments), _part_NN_context.json (bridging context containing the last 5 lines of the preceding segment as preceding_lines and the first 3 lines of the following segment as following_lines), and _split_manifest.json (the manifest).

Phase 1.5: Tone Anchoring (Large-Scale Translations Only)

Execute this phase when translating a single file > 1000 lines or multiple files, to ensure stylistic consistency.

1. Select a representative passage: Choose a passage from the source that is content-rich and stylistically representative (300–500 lines), preferring paragraphs that mix technical description with narrative.
2. Primary agent translates this passage: Translate it against the glossary and translation brief, producing a "tone sample" and writing it to _tone_sample.md.
3. Use of the tone sample: _tone_sample.md is passed to all sub-agents alongside user-samples.md as a style reference anchor.

Small-scale translations (handled directly by the primary agent) skip this phase.

Phase 2: Translation Execution

Small-Scale (Primary Agent Translates Directly, ≤ 1000 Lines)

Translate the full text against the following three materials and output to {filename}_zh.md (or the user-specified target language suffix) in the source file's directory:

• _glossary.md (temporary glossary generated in Phase 1)
• _translation_brief.md (temporary translation brief generated in Phase 1)
• {SKILL_DIR}/references/user-samples.md (user style samples, if present)

[TERM: ...] annotations: When a new term is encountered during translation that is not in _glossary.md, annotate it inline in the translation as [TERM: original → suggested rendering]. Do not list them separately; they will be processed in Phase 4.

Large-Scale (Sub-Agents Translate in Parallel, > 1000 Lines)

⚠️ Sub-agents are required: Large-scale translations (> 1000 lines or multiple files) must be processed in parallel through sub-agents. The primary agent must not directly translate segments. The primary agent's responsibilities are preparation, task dispatch, and result verification.

Dispatch a sub-agent for each segment using the template in references/subagent-prompt.md.

Sub-agent configuration:

• subagent_type: "general-purpose"
• model: "sonnet" (quality-first)
• Multiple sub-agents launched in parallel
• Each sub-agent receives: source segment, glossary, translation brief, bridging context, user style samples, tone sample
• Output requirements: Output must go to the designated {part}_zh.md file; generating merged files (e.g., _part_47-50_zh.md) is not permitted; translating beyond the assigned source range is not permitted.

Multi-file parallel strategy: Use TaskCreate/TaskList to track translation progress for each file/segment, and ensure all tasks are complete before proceeding to the next phase.

Error recovery (with failure criteria):

A sub-agent is considered to have failed if any of the following conditions is met:

1. The output file does not exist.
2. The output line count is less than 30% of the source line count.
3. The output contains large blocks of untranslated source text (10 or more consecutive lines identical to the source).
4. The output filename does not match expectations (e.g., a merged file was generated instead of individual segment files).

Handling procedure:

• Sub-agent failure → retry once with sonnet.
• Still failing → compile all failed segments, report the failure reasons and a list of affected segments to the user, and let the user decide how to proceed.
• The primary agent must not take over translation unless explicitly requested by the user.

Phase 3: Verification

Pre-Merge Verification

Inspect all translated segments before merging to confirm they meet standards and reduce post-merge issues.

Checklist:

1. Completeness check: Confirm that all segments have a corresponding translated file.
2. Filename check: Confirm there are no unexpected merged files (e.g., _part_47-50_zh.md).
3. Scope check: Spot-check several segments to confirm none extends beyond the source range.
4. Format compliance check: Executed by sub-agents, verifying against the formatting requirements in the translation brief generated in Phase 1:
   • Heading hierarchy is contiguous
   • Code blocks are properly closed
   • List indentation is correct
   • Table formatting is complete

Handling check failures:

• Problem segments found → compile a list and report to the user
• Ask the user whether corrections or re-translation are needed
• Execute corrections or re-translation after user confirmation

Automatic merge (split translations only):

python {SKILL_DIR}/scripts/merge_md.py --manifest {source_dir}/_parts/_split_manifest.json --output {source_dir}/{filename}_zh.md

The merge script automatically checks: heading hierarchy continuity, code block closure, and link integrity.

Primary agent review:

1. Confirm all sub-agent / segment translations are complete.
2. Execute the pre-merge verification (see checklist above).
3. Merge the split segments.
4. Process [TERM: ...] annotations for new terms.
5. Large files: quickly inspect segment boundaries (5 lines on each side) to ensure contextual continuity.
6. Multiple files: run a cross-file terminology consistency scan.

Optional: Refinement

The translation philosophy emphasizes rewriting over sentence-by-sentence rendering; high-quality translation execution already internalizes awareness of translationese. Refinement is an optional step, considered in the following scenarios:

• The user explicitly requests refinement.
• The primary agent identifies obvious translationese or stylistic inconsistency during review.

Refinement is executed by sub-agents under primary agent oversight. See references/refinement-guide.md for details.

Post-Merge Quality Check (Optional)

This step requires user input. If the user wishes, sub-agents can perform a quality check.

What is checked:

1. Format check: Executed by sub-agents; checks formatting standards of the final merged file.
2. Terminology consistency: Scans for consistent use of glossary terms throughout the translation.
3. Translationese detection: Checks for obvious translationese issues.
4. Stylistic consistency: Spot-checks multiple sections to verify uniform translation style.

How to execute:

• Ask the user whether to run the quality check.
• After user confirmation, sub-agents execute the check.
• Compile findings into a list and report to the user.
• The user decides whether corrections are needed.

Phase 4: Output Cleanup

1. Glossary writeback (mandatory; must not be skipped): Scan the translation for all [TERM: ...] annotations, compile the list of new terms added in this session, present the list to the user, and ask whether to write them to {SKILL_DIR}/references/user-glossary.md. If there are no new terms, explicitly inform the user: "No new terms were identified in this session."
2. Confirm the output file ({filename}_zh.md; the source file is never overwritten).
3. Clean up temporary files:

   rm -f _glossary.md _translation_brief.md _tone_sample.md
   rm -rf _parts/
   

4. Files that are not cleaned up (user-persisted assets):
   • references/user-glossary.md
   • references/user-samples.md
   • references/translation-brief-template.md
   • references/locale-styles.md

Important Notes

• Never overwrite the source file: Output files receive a language suffix (default: the target language code).
• Do not translate code blocks: This includes both inline code and fenced code blocks; comments within code may be translated.
• Preserve original formatting: Heading hierarchy, list indentation, table alignment, and blank line separation.
• Link handling: Translate link text; leave URLs unchanged.
• YAML frontmatter: Preserve as-is without translating.
• Default target locale: Defaults to Chinese mainland readers (zh-CN); other locales may be specified in the translation brief.
• Glossary takes precedence: Renderings specified in the glossary must be followed consistently throughout the entire text.
• Source language is unrestricted: Any source language is supported; the detected language is recorded in the translation brief.