chore: release v1.48.1

- chunk.ts: add --output-dir option so chunks write to output directory instead of source directory
- Refined workflow: split Review into Critical Review + Revision (5→6 steps)
- Add Europeanized language diagnosis for CJK targets

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Skills shared by Baoyu for improving daily work efficiency",
-    "version": "1.47.0"
+    "version": "1.48.1"
   },
   "plugins": [
     {

CHANGELOG.md

@@ -2,6 +2,18 @@
 
 English | [中文](./CHANGELOG.zh.md)
 
+## 1.48.1 - 2026-03-05
+
+### Features
+- `baoyu-translate`: add figurative language & metaphor mapping to analysis step — interprets metaphors, idioms, and implied meanings before translation instead of translating literally
+- `baoyu-translate`: add "meaning over words", "figurative language", and "emotional fidelity" translation principles to SKILL.md, refined workflow, and subagent prompt template
+
+## 1.48.0 - 2026-03-05
+
+### Features
+- `baoyu-translate`: add `--output-dir` option to chunk.ts — chunks now write to the translation output directory instead of the source file directory
+- `baoyu-translate`: improve refined workflow — split Review into Critical Review + Revision (5→6 steps), add Europeanized language diagnosis for CJK targets
+
 ## 1.47.0 - 2026-03-05
 
 ### Features

CHANGELOG.zh.md

@@ -2,6 +2,18 @@
 
 [English](./CHANGELOG.md) | 中文
 
+## 1.48.1 - 2026-03-05
+
+### 新功能
+- `baoyu-translate`：在分析阶段新增比喻语言与隐喻映射——翻译前先解读隐喻、习语和隐含意义，避免字面直译
+- `baoyu-translate`：新增"意义优先于字面"、"比喻语言解读"、"情感忠实度"三项翻译原则，同步更新 SKILL.md、精翻工作流和子代理提示词模板
+
+## 1.48.0 - 2026-03-05
+
+### 新功能
+- `baoyu-translate`：为 chunk.ts 新增 `--output-dir` 选项——分块文件现在写入翻译输出目录而非源文件目录
+- `baoyu-translate`：优化精翻工作流——将审校拆分为批判性审查 + 修订（5→6 步），新增中日韩目标语言的欧化表达诊断
+
 ## 1.47.0 - 2026-03-05
 
 ### 新功能

skills/baoyu-translate/SKILL.md

@@ -13,7 +13,7 @@ Scripts in `scripts/` subdirectory. `${SKILL_DIR}` = this SKILL.md's directory p
 
 | Script | Purpose |
 |--------|---------|
-| `scripts/chunk.ts` | Split markdown into chunks by AST blocks (sections, headings, paragraphs), with line/word fallback for oversized blocks |
+| `scripts/chunk.ts` | Split markdown into chunks by AST blocks (sections, headings, paragraphs), with line/word fallback for oversized blocks. Use `--output-dir <dir>` to write chunks into `<dir>/chunks/` instead of `<source-dir>/chunks/` |
 
 ## Preferences (EXTEND.md)
 
@@ -154,7 +154,8 @@ All intermediate and final files go into this directory:
 | `01-analysis.md` | Normal, Refined | Content analysis (domain, tone, terminology) |
 | `02-prompt.md` | Normal, Refined | Assembled translation prompt (used by subagent or inline) |
 | `03-draft.md` | Refined | Initial draft before review |
-| `04-review.md` | Refined | Reviewed version with fixes |
+| `04-critique.md` | Refined | Critical review findings (diagnosis only, no rewriting) |
+| `05-revision.md` | Refined | Revised translation based on critique |
 | `chunks/` | Chunked | Source chunks + translated chunks |
 | `chunks/chunk-01.md` | Chunked | Source chunk |
 | `chunks/chunk-01-draft.md` | Chunked | Translated chunk |
@@ -178,7 +179,7 @@ Before translating chunks:
 
 1. **Extract terminology**: Scan entire document for proper nouns, technical terms, recurring phrases
 2. **Build session glossary**: Merge extracted terms with loaded glossaries, establish consistent translations
-3. **Split into chunks**: Use `${BUN_X} ${SKILL_DIR}/scripts/chunk.ts <file> [--max-words <chunk_max_words>]`
+3. **Split into chunks**: Use `${BUN_X} ${SKILL_DIR}/scripts/chunk.ts <file> [--max-words <chunk_max_words>] [--output-dir <output-dir>]`
    - Parses markdown AST (headings, paragraphs, lists, code blocks, tables, etc.)
    - Splits at markdown block boundaries to preserve structure
    - If a single block exceeds the threshold, falls back to line splitting, then word splitting
@@ -194,17 +195,20 @@ Before translating chunks:
 6. **Merge**: Once all subagents complete, combine translated chunks in order, prepend frontmatter if present → save as `03-draft.md` (refined) or `translation.md` (normal)
 7. All intermediate files (source chunks + translated chunks) are preserved in `chunks/`
 
-**After chunked draft is merged**, return control to main agent for review and polish (Step 4).
+**After chunked draft is merged**, return control to main agent for critical review, revision, and polish (Step 4).
 
 ### Step 4: Translate & Refine
 
 **Translation principles** (apply to all modes):
 
 - **Accuracy first**: Facts, data, and logic must match the original exactly
-- **Natural flow**: Use idiomatic target language word order; break long sentences into shorter ones
+- **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 language
+- **Figurative language**: Interpret metaphors, idioms, and figurative expressions by their intended meaning rather than translating them word-for-word. When a source-language image does not carry the same connotation in the target language, replace it with a natural expression that conveys the same idea and emotional effect
+- **Emotional fidelity**: Preserve the emotional connotations of word choices, not just their dictionary meanings. Words that carry subjective feelings (e.g., "alarming", "haunting") should be rendered to evoke the same response in target-language readers
+- **Natural flow**: Use idiomatic target language word order and sentence patterns; break or restructure sentences freely when the source structure doesn't work naturally in the target language
 - **Terminology**: Use standard translations; 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 structure and meaning; do not add, remove, or editorialize
+- **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, concepts, or cultural references that target readers may not understand — due to jargon, cultural gaps, or domain-specific knowledge — add a concise explanatory note in parentheses immediately after the term. The note should explain *what it means* in plain language, not just provide the English original. Format: `译文（English original，通俗解释）`. Calibrate annotation depth to the target audience: general readers need more notes than technical readers. Only add notes where genuinely needed; do not over-annotate obvious terms.
 
 #### Quick Mode
@@ -213,26 +217,27 @@ Translate directly → save to `translation.md`.
 
 #### Normal Mode
 
-1. **Analyze** → `01-analysis.md` (domain, tone, audience, terminology, reader comprehension challenges)
+1. **Analyze** → `01-analysis.md` (domain, tone, audience, terminology, reader comprehension challenges, figurative language & metaphor mapping)
 2. **Assemble prompt** → `02-prompt.md` (translation instructions with inlined context)
 3. **Translate** (following `02-prompt.md`) → `translation.md`
 
 After completion, prompt user: "Translation saved. To further review and polish, reply **继续润色** or **refine**."
 
-If user continues, proceed with review → polish (same as refined mode Steps 3-4 below), saving `03-draft.md` (rename current `translation.md`), `04-review.md`, and updated `translation.md`.
+If user continues, proceed with critical review → revision → polish (same as refined mode Steps 4-6 below), saving `03-draft.md` (rename current `translation.md`), `04-critique.md`, `05-revision.md`, and updated `translation.md`.
 
 #### Refined Mode
 
 Full workflow for publication quality. See [references/refined-workflow.md](references/refined-workflow.md) for detailed guidelines per step.
 
-The subagent (if used in Step 3.1) only handles the initial draft. All subsequent steps are handled by the main agent, which may delegate to subagents at its discretion.
+The subagent (if used in Step 3.1) only handles the initial draft. All subsequent steps (critical review, revision, polish) are handled by the main agent, which may delegate to subagents at its discretion.
 
 Steps and saved files (all in output directory):
-1. **Analyze** → `01-analysis.md` (domain, tone, terminology, reader comprehension challenges)
+1. **Analyze** → `01-analysis.md` (domain, tone, terminology, reader comprehension challenges, figurative language & metaphor mapping)
 2. **Assemble prompt** → `02-prompt.md` (translation instructions with inlined context)
 3. **Draft** → `03-draft.md` (initial translation with translator's notes; from subagent if chunked)
-4. **Review** → `04-review.md` (accuracy, naturalness, terminology fixes)
-5. **Polish** → `translation.md` (final publication-quality translation)
+4. **Critical review** → `04-critique.md` (diagnosis only: accuracy, Europeanized language, strategy execution, expression issues)
+5. **Revision** → `05-revision.md` (apply all critique findings to produce revised translation)
+6. **Polish** → `translation.md` (final publication-quality translation)
 
 Each step reads the previous step's file and builds on it.
 

skills/baoyu-translate/references/refined-workflow.md

@@ -4,8 +4,8 @@ This file provides detailed guidelines for each workflow step. Steps are shared
 
 - **Quick**: Translate only (no steps from this file)
 - **Normal**: Step 1 (Analysis) → Translate
-- **Refined**: Step 1 (Analysis) → Step 2 (Draft) → Step 3 (Review) → Step 4 (Polish)
-- **Normal → Upgrade**: After normal mode, user can continue with Step 3 → Step 4
+- **Refined**: Step 1 (Analysis) → Step 2 (Draft) → Step 3 (Review) → Step 4 (Revision) → Step 5 (Polish)
+- **Normal → Upgrade**: After normal mode, user can continue with Step 3 → Step 4 → Step 5
 
 All intermediate results are saved as files in the output directory.
 
@@ -63,10 +63,26 @@ For each identified challenge, note:
 2. Why it may confuse target readers
 3. A concise plain-language explanation to use as a translator's note
 
-### 1.7 Translation Challenges
+### 1.7 Figurative Language & Metaphor Mapping
 
+Identify all metaphors, similes, idioms, and figurative expressions in the source. For each:
+
+1. **Original expression**: The exact phrase
+2. **Intended meaning**: What the author is actually communicating (the idea behind the image)
+3. **Literal translation risk**: Would a word-for-word translation sound unnatural, lose the connotation, or confuse target readers?
+4. **Target-language approach**: One of:
+   - **Interpret**: Discard the source image entirely, express the intended meaning directly in natural target language
+   - **Substitute**: Replace with a target-language idiom or image that conveys the same idea and emotional effect
+   - **Retain**: Keep the original image if it works equally well in the target language
+
+Also flag:
+- **Emotional connotations carried by word choice**: Words like "alarming" that convey subjective feeling, not just objective description — note the emotional effect to preserve
+- **Implied meanings**: Sentences where the surface meaning is simple but the implication is richer — note what the author really means so the translator can convey the full intent
+
+### 1.8 Structural & Creative Challenges
+
+- Complex sentence patterns (long subordinate clauses, nested modifiers, participial phrases) that need restructuring for natural target-language flow
 - Structural challenges (wordplay, ambiguity, puns that don't translate)
-- Passages where literal translation would lose meaning
 - Content where the author's voice or humor requires creative adaptation
 
 **Save `01-analysis.md`** with:
@@ -95,8 +111,12 @@ Implicit assumptions: [unstated premises]
 - [term/passage] → [why confusing] → [proposed note]
 - ...
 
-## Translation Challenges
-[structural issues, creative adaptation needs]
+## Figurative Language & Metaphor Mapping
+- [original expression] → [intended meaning] → [approach: interpret/substitute/retain] → [suggested rendering]
+- ...
+
+## Structural & Creative Challenges
+[sentence restructuring needs, wordplay, creative adaptation needs]
 ```
 
 ## Step 2: Assemble Translation Prompt
@@ -115,60 +135,117 @@ Translate the full content following `02-prompt.md`:
 
 - Use the terminology decisions from Step 1 consistently
 - Match the identified tone and register
-- Break complex sentences into natural target-language patterns
+- Break complex sentences into natural target-language patterns; restructure freely when the source sentence order doesn't work in the target language
+- Interpret figurative language by meaning: translate what the author means, not the literal image, following the metaphor mapping from Step 1
+- Preserve the emotional tone and connotations of word choices, not just their dictionary meanings
 - Preserve all formatting and structure
 - First occurrence of technical terms: translated term (original in parentheses)
 - Add translator's notes for comprehension challenges identified in Step 1: use parentheses with a plain-language explanation, e.g., `译文（English original，通俗解释）`
 - Only annotate where genuinely needed — do not over-explain obvious terms
 
-## Step 4: Review
+## Step 4: Critical Review
 
-The main agent reviews the draft. Save reviewed version to `04-review.md`.
+The main agent critically reviews the draft against the source. Save review findings to `04-critique.md`. This step produces **diagnosis only** — no rewriting yet.
 
-Systematically review against these criteria:
-
-### Accuracy Check
-- Compare each paragraph against the original
+### 4.1 Accuracy & Completeness
+- Compare each paragraph against the original, sentence by sentence
 - Verify all facts, numbers, dates, and proper nouns
-- Ensure no content was accidentally added, removed, or altered
+- Flag any content accidentally added, removed, or altered
 - Check that technical terms match glossary consistently throughout
+- Verify no paragraphs or sections were skipped
 
-### Naturalness Check
-- Read the translation as if it were original content (not a translation)
-- Flag sentences that sound like "translationese" — awkward word order, calques, unnatural phrasing
-- Check paragraph transitions and logical flow
-- Verify sentence length feels natural for target language
+### 4.2 Europeanized Language Diagnosis (for CJK targets)
+- **Unnecessary connectives**: Overuse of 因此/然而/此外/另外 where context already implies the relationship
+- **Passive voice abuse**: Excessive 被/由/受到 where active voice is more natural
+- **Noun pile-up**: Long modifier chains that should be broken into shorter clauses
+- **Cleft sentences**: Unnatural "是...的" structures calqued from English "It is...that"
+- **Over-nominalization**: Abstract nouns where verbs or adjectives would be more natural (e.g., "进行了讨论" → "讨论了")
+- **Awkward pronouns**: Overuse of 他/她/它/我们/你 where they can be omitted
 
-### Terminology Consistency
-- Verify each glossary term is translated the same way throughout
-- Check proper nouns are handled consistently (transliterated vs. kept in original)
-- Verify annotations appear on first occurrence only
+### 4.3 Strategy Execution
+- Were the translation strategies from `02-prompt.md` actually followed?
+- Did the translator apply the tone and register identified in analysis?
+- Were comprehension challenges from `01-analysis.md` addressed with appropriate notes?
+- Were glossary terms used consistently?
 
-### Cultural Adaptation & Translator's Notes
-- Are cultural references explained where needed?
+### 4.4 Expression & Logic
+- Flag sentences that read like "translationese" — unnatural word order, calques, stiff phrasing
+- Check logical flow between sentences and paragraphs
+- Identify where sentence restructuring would improve readability
+- Note where the target language idiom was missed (e.g., English metaphor translated literally instead of finding a target-language equivalent)
+
+### 4.5 Translator's Notes Quality
+- Are notes accurate, concise, and genuinely helpful?
+- Identify missed comprehension challenges that need notes
+- Flag over-annotations on terms obvious to the target audience
+- Check that cultural references are explained where needed
+
+### 4.6 Cultural Adaptation
 - Do metaphors and idioms work in the target language?
 - Are any references potentially confusing or offensive in the target culture?
-- Check translator's notes: are they accurate, concise, and genuinely helpful?
-- Identify any missed comprehension challenges that should have notes
-- Remove over-annotations on terms that are obvious to the target audience
+- Could any passage be misinterpreted due to cultural context differences?
 
-## Step 5: Polish
+**Save `04-critique.md`** with:
+```
+## Accuracy & Completeness
+- [issue]: [location] — [description]
+- ...
+
+## Europeanized Language Issues
+- [issue type]: [example from draft] → [suggested fix]
+- ...
+
+## Strategy Execution
+- [strategy]: [followed/missed] — [details]
+- ...
+
+## Expression & Logic
+- [location]: [problem] → [suggestion]
+- ...
+
+## Translator's Notes
+- [add/remove/revise]: [term] — [reason]
+- ...
+
+## Cultural Adaptation
+- [issue]: [description] — [suggestion]
+- ...
+
+## Summary
+[Overall assessment: X critical issues, Y improvements, Z minor suggestions]
+```
+
+## Step 5: Revision
+
+Apply all findings from `04-critique.md` to produce a revised translation. Save to `05-revision.md`.
+
+The revision reads `03-draft.md` (the original draft) and `04-critique.md` (the review findings), and may also refer back to the source text and `01-analysis.md`:
+
+- Fix all accuracy issues identified in the critique
+- Rewrite Europeanized expressions into natural target-language patterns
+- Apply missed translation strategies
+- Restructure stiff or awkward sentences for fluency
+- Add, remove, or revise translator's notes per critique recommendations
+- Improve transitions between paragraphs
+- Adapt cultural references as suggested
+
+## Step 6: Polish
 
 Save final version to `translation.md`.
 
-Final pass addressing all issues from the review:
+Final pass on `05-revision.md` for publication quality:
 
-- Fix all accuracy issues found in review
-- Rewrite unnatural sentences for fluency
-- Improve transitions between paragraphs
-- Ensure the translation reads as engaging, native-quality content
-- Verify formatting is preserved correctly
+- Read the entire translation as a standalone piece — does it flow as native content?
+- Smooth any remaining rough transitions between paragraphs
+- Ensure the narrative voice is consistent throughout
 - For storytelling-style content: ensure the narrative flow draws readers in
-- Final consistency check on terminology
+- Final consistency check on terminology across the full text
+- Verify formatting is preserved correctly (headings, bold, links, code blocks)
+- Remove any remaining traces of translationese
 
 ## Subagent Responsibility
 
-Each subagent (one per chunk) is responsible **only** for producing the initial draft of its chunk (Step 3). The main agent assembles the shared prompt (Step 2), spawns all subagents in parallel, then takes over for review (Step 4) and polish (Step 5). The main agent may delegate review or polish to subagents at its own discretion.
+Each subagent (one per chunk) is responsible **only** for producing the initial draft of its chunk (Step 3). The main agent assembles the shared prompt (Step 2), spawns all subagents in parallel, then takes over for critical review (Step 4), revision (Step 5), and polish (Step 6). The main agent may delegate revision or polish to subagents at its own discretion.
 
 ## Chunked Refined Translation
 
@@ -178,8 +255,9 @@ When content exceeds the chunk threshold (see Defaults in SKILL.md) and uses ref
 2. Main agent assembles translation prompt → `02-prompt.md`
 3. Split into chunks → `chunks/`
 4. Spawn one subagent per chunk in parallel (each reads `02-prompt.md` for shared context) → merge all results into `03-draft.md`
-5. Main agent reviews the merged draft → `04-review.md`
-6. Main agent polishes → `translation.md`
+5. Main agent critically reviews the merged draft → `04-critique.md`
+6. Main agent revises based on critique → `05-revision.md`
+7. Main agent polishes → `translation.md`
 7. Final cross-chunk consistency check:
    - Check terminology consistency across chunk boundaries
    - Verify narrative flow between chunks

skills/baoyu-translate/references/subagent-prompt-template.md

@@ -21,7 +21,7 @@ You are a professional translator. Your task is to translate markdown content fr
 
 ## Content Background
 
-{Inlined from 01-analysis.md if analysis exists: quick summary, core argument, author background, writing context, tone assessment.}
+{Inlined from 01-analysis.md if analysis exists: quick summary, core argument, author background, writing context, tone assessment, figurative language & metaphor mapping.}
 
 ## Glossary
 
@@ -38,10 +38,13 @@ The following terms or references may confuse target readers. Add translator's n
 ## Translation Principles
 
 - **Accuracy first**: Facts, data, and logic must match the original exactly
-- **Natural flow**: Use idiomatic {target_lang} word order; break long sentences into shorter ones
+- **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. Refer to the Figurative Language section in Content Background (if provided) for pre-analyzed metaphor mappings
+- **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 structure and meaning; do not add, remove, or editorialize
+- **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. Only annotate where genuinely needed for the target audience.
 ```
 

skills/baoyu-translate/scripts/chunk.ts

@@ -10,6 +10,7 @@ import type { Root, Content } from "mdast"
 const args = process.argv.slice(2)
 const file = args.find(a => !a.startsWith("--"))
 const maxWords = parseInt(args[args.indexOf("--max-words") + 1] || "5000")
+const outputDir = args.indexOf("--output-dir") !== -1 ? args[args.indexOf("--output-dir") + 1] : ""
 
 if (!file) {
   console.error("Usage: chunk.ts <file> [--max-words 5000]")
@@ -114,7 +115,7 @@ for (const b of blocks) {
 }
 if (cur.length > 0) chunks.push({ blocks: cur, words: curWords })
 
-const dir = join(dirname(file), "chunks")
+const dir = outputDir ? join(outputDir, "chunks") : join(dirname(file), "chunks")
 mkdirSync(dir, { recursive: true })
 
 chunks.forEach((chunk, i) => {