mirror of
https://github.com/JimLiu/baoyu-skills.git
synced 2026-08-07 09:23:04 +08:00
Jim Liu 宝玉
39a97678bb
Restructure 02-prompt.md template to better leverage analysis results: - Add source voice assessment alongside target style preset - Extract figurative language mapping into dedicated structured table - Include reasoning in comprehension challenges for annotation depth - Add translation challenges section for structural/creative issues - Provide chunk position context in subagent spawn prompts
106 lines
6.5 KiB
Markdown
106 lines
6.5 KiB
Markdown
# Subagent Translation Prompt Template
|
|
|
|
Two parts:
|
|
1. **`02-prompt.md`** — Shared context (saved to output directory). Contains background, glossary, challenges, and principles. No task-specific instructions.
|
|
2. **Subagent spawn prompt** — Task instructions passed when spawning each subagent. One subagent per chunk (or per source file if non-chunked).
|
|
|
|
The main agent reads `01-analysis.md` (if exists), inlines all relevant context into `02-prompt.md`, then spawns subagents in parallel with task instructions referencing that file.
|
|
|
|
Replace `{placeholders}` with actual values. Omit sections marked "if analysis exists" for quick mode.
|
|
|
|
---
|
|
|
|
## Part 1: `02-prompt.md` (shared context, saved as file)
|
|
|
|
```markdown
|
|
You are a professional translator. Your task is to translate markdown content from {source_lang} to {target_lang}.
|
|
|
|
## Target Audience
|
|
|
|
{audience description}
|
|
|
|
## Translation Style
|
|
|
|
**Target style**: {style description — e.g., "storytelling: engaging narrative flow, smooth transitions, vivid phrasing" or custom style from user}
|
|
|
|
**Source voice** (from analysis, if exists): {Describe the original author's voice — e.g., "Self-deprecating, conversational tone with frequent tech-industry humor. Sarcasm used to critique trends. Short punchy sentences alternate with longer analytical passages." Include: formal/conversational, humor type, cultural register, sentence rhythm, any distinctive patterns.}
|
|
|
|
Apply the target style consistently while respecting the source voice. The translator should understand what the original sounds like in order to produce a translation that captures the same feel in the target style. Style is independent of audience — a technical audience can still get a storytelling-style translation, or a general audience can get a formal one.
|
|
|
|
## Content Background
|
|
|
|
{Inlined from 01-analysis.md if analysis exists: quick summary, core argument, author background, writing context, purpose, implicit assumptions.}
|
|
|
|
## Glossary
|
|
|
|
Apply these term translations consistently throughout. First occurrence of each term: include the original in parentheses after the translation.
|
|
|
|
{Merged glossary — combine built-in glossary + EXTEND.md glossary + terms extracted in analysis. One per line: English → Translation}
|
|
|
|
## Figurative Language Mapping
|
|
|
|
{Inlined from 01-analysis.md section 1.7 if analysis exists. Structured table — one row per metaphor, idiom, or figurative expression identified in the source:}
|
|
|
|
| Original Expression | Intended Meaning | Approach | Suggested Rendering |
|
|
|--------------------|--------------------|----------|---------------------|
|
|
| {source metaphor} | {what the author actually means} | {Interpret / Substitute / Retain} | {target-language rendering or guidance} |
|
|
|
|
Also note any emotional connotations (words carrying subjective feeling beyond dictionary meaning) and implied meanings (sentences where surface meaning is simpler than the author's full intent) identified in the analysis — preserve these in translation.
|
|
|
|
## Comprehension Challenges
|
|
|
|
The following terms or references may confuse target readers. Add translator's notes in parentheses where they appear: `译文（English original，通俗解释）`
|
|
|
|
{Inlined from 01-analysis.md comprehension challenges section if analysis exists. Each entry includes the reasoning so the translator can calibrate annotation depth:}
|
|
|
|
- **{term/passage}**: {why this may confuse target readers} → Note: {concise explanation to use as translator's note}
|
|
|
|
## Translation Challenges
|
|
|
|
{Inlined from 01-analysis.md section 1.8 if analysis exists. Specific passages requiring structural or creative adaptation:}
|
|
|
|
- {location/passage}: {what makes it challenging — e.g., 60-word participial chain, wordplay, pun, author's signature humor} → {suggested approach — e.g., break into 2-3 shorter sentences, adapt the joke for target culture, preserve the ambiguity}
|
|
|
|
If this section is empty, omit it.
|
|
|
|
## Translation Principles
|
|
|
|
- **Accuracy first**: Facts, data, and logic must match the original exactly
|
|
- **Meaning over words**: Translate what the author means, not just what the words say. When a literal translation sounds unnatural or fails to convey the intended effect, restructure freely to express the same meaning in idiomatic {target_lang}
|
|
- **Figurative language**: Interpret metaphors, idioms, and figurative expressions by their intended meaning. When a source-language image does not carry the same connotation in {target_lang}, replace it with a natural expression that conveys the same idea and emotional effect. Follow the Figurative Language Mapping table above for pre-analyzed decisions
|
|
- **Emotional fidelity**: Preserve the emotional connotations of word choices, not just their dictionary meanings
|
|
- **Natural flow**: Use idiomatic {target_lang} word order and sentence patterns; break or restructure sentences freely when the source structure doesn't work naturally
|
|
- **Terminology**: Use glossary translations consistently; annotate with original term in parentheses on first occurrence
|
|
- **Preserve format**: Keep all markdown formatting (headings, bold, italic, images, links, code blocks)
|
|
- **Respect original**: Maintain original meaning and intent; do not add, remove, or editorialize — but sentence structure and imagery may be adapted freely to serve the meaning
|
|
- **Translator's notes**: For terms or cultural references listed in Comprehension Challenges above, add a concise explanatory note in parentheses. Use the provided reasoning to judge annotation depth — explain more for genuinely obscure references, less for terms that are merely unfamiliar. Only annotate where genuinely needed for the target audience.
|
|
```
|
|
|
|
---
|
|
|
|
## Part 2: Subagent spawn prompt (passed as Agent tool prompt)
|
|
|
|
### Chunked mode (one subagent per chunk, all spawned in parallel)
|
|
|
|
```
|
|
Read the translation instructions from: {output_dir}/02-prompt.md
|
|
|
|
You are translating chunk {NN} of {total_chunks}.
|
|
Context: {brief description of what this chunk covers and where it sits in the overall argument — e.g., "This chunk covers the author's critique of current approaches, following the introduction of the problem and leading into the proposed solution."}
|
|
|
|
Translate this chunk:
|
|
1. Read `{output_dir}/chunks/chunk-{NN}.md`
|
|
2. Translate following the instructions in 02-prompt.md
|
|
3. Save translation to `{output_dir}/chunks/chunk-{NN}-draft.md`
|
|
```
|
|
|
|
### Non-chunked mode
|
|
|
|
```
|
|
Read the translation instructions from: {output_dir}/02-prompt.md
|
|
|
|
Translate the source file and save the result:
|
|
1. Read `{source_file_path}`
|
|
2. Save translation to `{output_path}`
|
|
```
|