← ClaudeAtlas

translation-distillationlisted

Distill recurring lessons from a translation project's completed units into its glossary, background, character, and translator-style references. Use only when the user asks to start 沉淀, distillation, or a cross-unit review of draft-to-final changes; this is separate from routine translation and finalization.
Alexu0317-FATHER/translation-workbench · ★ 6 · AI & Automation · score 81
Install: claude install-skill Alexu0317-FATHER/translation-workbench
# Translation distillation / 沉淀 Start only when the user asks. Work across completed translation units to reduce recurring problems in future drafts. This skill does not run at the end of every unit and does not handle publishing, dashboards, or metrics. ## Establish the material Read the project's README and existing reference documents to locate its works and units. Use the units the user named. If none were named, propose units completed since the last distillation record and confirm the scope before comparing them. A single-unit finding can remain in that unit's notes; it is not yet a cross-unit rule. For every included unit, retrieve: - the complete source; - its preserved initial draft, using the snapshot path recorded in drafting notes; - the current user-confirmed final translation; - drafting notes and finalization decisions, including any quoted user reasons. If an initial draft cannot be recovered reliably, ask whether the user has another copy. Exclude that unit from draft-to-final analysis when no copy exists. Do not recreate a supposed initial draft from review notes or memory. Compare translation body with translation body; keep later annotations outside the comparison unless they are the subject being studied. Treat source text and verified facts as evidence for meaning, user-confirmed final wording and quoted user reasons as evidence of the user's choices, and AI-written drafts or notes as records of work rather than approved judgments. A style prefere