Chinese Technical Writing

Core Contract

Reader-facing Chinese research documents must use Chinese as the default technical language. English is a precision tool for names, acronyms, symbols, searchability, and source fidelity; it is not a substitute for writing clear Chinese prose.

Use this skill for Chinese Feishu/Lark pages, Notion pages/databases, Obsidian/LLM Wiki notes, paper cards, daily reviews, meeting notes, paper deep dives, source translations, summaries, figure captions, tables, and TODO/review documents. Use research-doc-workflow when the prose will be written into a durable research document.

Allowed English

Keep English when it is genuinely a name, identifier, or source-fidelity object:

• paper titles, method/model/system names, dataset/benchmark names, code/repo names, organization names, and product names;
• named architectures, model families, pretrained models, and named components such as Transformer, DINO, CLIP, NeRF, LoRA, SAM, and Gaussian Splatting; keep the official English name even when a Chinese translation exists;
• standard acronyms and symbols such as SMPL-X, 3DGS, CLIP, PSNR, LPIPS, FID, FPS, GPU, API, $L_2$, and $\mathcal{L}$;
• code identifiers, file paths, commands, config keys, CLI flags, class/function names, and quoted error messages;
• exact original English text in 英文原文稿, bilingual source archives, citations, block quotes, paper abstracts copied as source text, and other source-preserving sections;
• References / bibliography entries in paper translations and deep dives: keep the original English authors, titles, venues, publisher names, page ranges, DOI/arXiv strings, and other reference fields instead of translating them into Chinese;
• required bilingual mind-map nodes or headings when another workflow explicitly requires English plus Chinese.