chinese-content-writing-guideline

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Chinese Content Writing Guidelines

繁体中文内容写作指南

This skill provides comprehensive writing guidelines for producing high-quality 正體中文 Traditional Chinese (zh-TW) content. Apply these rules to ensure consistent language, structure, tone, and terminology aligned with Taiwan conventions.

本技能提供高质量繁体中文（zh-TW）内容的全面写作指南。遵循这些规则，可确保语言、结构、语气和术语符合台湾地区的规范。

Language and Formatting

语言与格式

Write in Traditional Chinese 正體中文 (zh-TW) with full-width punctuation（，。、；：「」『』（）！？）
Always insert a single space between Chinese characters and alphanumeric characters (e.g.,
```
使用 Docker 建立
```
)
Use standard Taiwan Traditional Chinese terminology for technical terms
Address readers as 「讀者」「大家」「各位」 or 「你」, never 「您」
Refer to the author as 「我」, never 「我們」

使用繁体中文（正體中文）（zh-TW）及全角标点（，。、；：「」『』（）！？）进行写作
中文字符与字母数字字符之间始终保留一个空格（例如：
```
使用 Docker 建立
```
）
技术术语采用台湾标准繁体中文表述
称呼读者为「讀者」「大家」「各位」或「你」，禁止使用「您」
自称使用「我」，禁止使用「我們」

Structure

结构

Use inverted pyramid structure: core conclusion and scope first, supporting evidence second
Opening paragraph states the core conclusion and scope directly
Subsequent paragraphs provide evidence and limitations
Closing paragraph must not use slogan-style endings
Use natural paragraphs with
```
##
```
and
```
###
```
subheadings
Avoid bullet lists unless explicitly requested or justified; prefer prose
Use markdown reference-style links for external sources only, not for internal links. Each reference link should appear only once in the article.
Format all reference-style links using markdown so they display as "links." Use the webpage title (curl fetch it!) as the link text for each reference-style link.

采用倒金字塔结构：先给出核心结论与范围，再提供支撑证据
开篇段落直接说明核心结论与范围
后续段落提供证据与局限性说明
结尾段落禁止使用口号式表述
使用自然段落搭配
```
##
```
和
```
###
```
子标题
除非明确要求或合理必要，否则避免使用项目符号列表，优先采用散文式表述
仅对外部来源使用Markdown参考式链接，内部链接不适用。每篇文章中每个参考链接仅出现一次
所有参考式链接需使用Markdown格式，显示为「链接」。链接文本使用网页标题（可通过curl获取）

Tone and Style

语气与风格

Friendly yet professional; approachable expert, not academic
Neutral, restrained, verifiable
Prioritize reader comprehension over ornate rhetoric
Factual presentation with clear argumentation

友好且专业：以平易近人的专家视角表述，避免学术化风格
中立、克制、可验证
优先保障读者理解，避免华丽辞藻
事实陈述清晰，论证逻辑明确

Output Principles

输出原则

Facts First: All judgments must rest on verifiable data, case studies, or explicit logic. No vague attributions like 「研究指出」 or 「資料顯示」
Direct Statement: Prefer neutral, verifiable declarative and conditional sentences
De-templated Rhythm: Avoid mechanical three-point structures and symmetrical parallelism
Clear Communication: One point per sentence. Break long sentences with commas or semicolons

事实优先：所有判断必须基于可验证的数据、案例研究或明确逻辑。禁止使用「研究指出」或「資料顯示」这类模糊归因
直接表述：优先使用中立、可验证的陈述句与条件句
去模板化节奏：避免机械的三点式结构与对称排比
清晰沟通：每句仅表达一个要点。使用逗号或分号拆分长句

Hard Constraints

硬性约束

Rhetorical Device Quotas

修辞手法配额

Contrastive Construction (「不是…是」): max once per post
Parallelism/Tricolons: max once per post, max 3 sub-items, no semantic redundancy
Rhetorical Questions: max once per post, must not chain >2, concrete answer must follow
Em-dash (——): max twice per post, only for essential qualification. Never use it twice per section. Must not be used to stack adjectives or emotional content.

对比结构（「不是…是」）：每篇内容最多使用1次
排比/三句式：每篇内容最多使用1次，子项不超过3个，禁止语义冗余
反问句：每篇内容最多使用1次，禁止连续使用超过2个，且必须紧跟具体答案
破折号（——）：每篇内容最多使用2次，仅用于必要的限定说明。同一章节内禁止使用2次，不得用于堆叠形容词或情感化内容

Punctuation Constraint

标点约束

Avoid using colons in the middle of sentences: Use commas instead to revise them into smooth sentences. This does not apply to bulleted or listed items.

禁止在句中使用冒号：改用逗号改写为流畅的句子。此规则不适用于项目符号或列表项

Banned Phrases

禁用短语

Never use the following expressions:

「總的來說」「不只...更...」「不僅...也...」「...能有效...」「往往」「至關重要」「精心打造」「確保」「直接講」「先講」「提醒我們」「差別不在於...而在於...」「一個...另一個」「就像...」「表面上...，...時，可能截然不同」「這不是...是...」「...問題也值得關注」「一個事實」「關鍵差異」「最可怕的不是...」「核心問題」「不是...而是...」「令人不安的事實」「坐不住」「系統性地」「很精準」「只有...才能...」「誠實面對」「不舒服」「不太舒服」「很清楚」「講清楚」「非常清楚」「清晰」「精準地」

禁止使用以下表述：

Additional Prohibitions

其他禁令

Avoid reduplicated words
Avoid hedging phrases like 「可以說」「某種程度上」「在多數情況下」; replace with conditional qualifications
Avoid using "mirror" to describe feelings or things.
Avoid saying that this topic makes you feel uncomfortable, uneasy, or slightly offended, especially when discussing subjects such as cybersecurity, attacks, AI, ethics, philosophy, and psychology.
Utilize fewer metaphors and focus more on describing the facts.

避免使用叠词
避免使用「可以說」「某種程度上」「在多數情況下」这类模糊表述；改用条件限定
避免使用「鏡像」描述感受或事物
禁止提及该主题让你感到不舒服、不安或略有冒犯，尤其是在讨论网络安全、攻击、AI、伦理、哲学和心理学等主题时
减少比喻使用，聚焦事实描述

Alternative Patterns

替代范式

When tempted to use restricted devices, use instead:

Direct Conclusion + Evidence: State judgment first, then provide support
Conditional Sentence: 「在 X 條件下，Y 成立；超出範圍不保證」
Subheading + Short Paragraph: 2-4 lines addressing one aspect
Definition-Scope-Example: Define concept, specify scope, give one example

当你想使用受限手法时，可改用以下方式：

直接结论+证据：先给出判断，再提供支撑
条件句：「在 X 條件下，Y 成立；超出範圍不保證」
子标题+短段落：2-4行文字阐述一个方面
定义-范围-示例：定义概念、明确范围、给出一个示例

Automatic Rewrite Rules

自动改写规则

Apply these transformations when a restricted pattern appears:

「不是…是」 → 「核心重點在於…；次要面向為…」
Tricolon parallelism with redundant items → consolidate into one prose paragraph
Rhetorical question → declarative problem-and-answer format
Consecutive em-dashes → extract into independent sentence or conditional qualification
When an English term appears multiple times, check for a common zh-TW translation or abbreviation. If found, present the original term with its Chinese equivalent the first time, then use only the Chinese version thereafter. This rule does not apply to proper nouns, including personal names.

当出现受限范式时，应用以下转换：

「不是…是」 → 「核心重點在於…；次要面向為…」
存在冗余项的三句式排比 → 合并为一个散文段落
反问句 → 陈述句形式的问题-答案格式
连续破折号 → 提取为独立句子或条件限定
当英文术语多次出现时，检查是否有通用的zh-TW翻译或缩写。若有，首次出现时同时呈现原术语及其中文对应译法，后续仅使用中文译法。此规则不适用于专有名词（包括人名）

Review Checklist

审核清单

Before finalizing, verify every item:

Do consecutive paragraph openings use the same rhetorical device? Rewrite if yes.
Do any restricted devices exceed their quota? Retain only the most necessary instance.
Does each key claim have evidence? Downgrade unsupported claims to hypotheses.
Are there unsourced strong assertions? Rewrite to conditional qualifications.
Are sentences overlong? Split into short sentences with clear subject-verb-object structure.
Are spaces correctly placed between Chinese and alphanumeric characters?
Is there English term appears multiple times?

定稿前，逐一验证以下项目：

连续段落开头是否使用相同修辞手法？若是则改写
受限手法是否超出配额？仅保留最必要的实例
每个关键主张是否有证据支撑？将无依据的主张降级为假设
是否存在无来源的强硬断言？改写为条件限定表述
句子是否过长？拆分为主谓宾结构清晰的短句
中文字符与字母数字字符之间的空格是否正确？
是否有英文术语多次出现？

Reference: Terminology Mappings

参考：术语对应表

When writing content, apply these Traditional Chinese mappings: create = 建立, object = 物件, queue = 佇列, stack = 堆疊, information = 資訊, invocation = 呼叫, code = 程式碼, running = 執行, library = 函式庫, schematics = 原理圖, building = 建構, Setting up = 設定, package = 套件, video = 影片, for loop = for 迴圈, class = 類別, Concurrency = 平行處理, Transaction = 交易, Transactional = 交易式, Code Snippet = 程式碼片段, Code Generation = 程式碼產生器, Any Class = 任意類別, Scalability = 延展性, Dependency Package = 相依套件, Dependency Injection = 相依性注入, Reserved Keywords = 保留字, Metadata = Metadata, Clone = 複製, Memory = 記憶體, Built-in = 內建, Global = 全域, Compatibility = 相容性, Function = 函式, Refresh = 重新整理, document = 文件, example = 範例, demo = 展示, quality = 品質, tutorial = 指南, recipes = 秘訣, byte = 位元組, bit = 位元, context = 脈絡, tech stack = 技術堆疊, equation = 方程式, activate = 啟動、觸發, feedback = 回饋

创作内容时，需遵循以下繁体中文对应关系：create = 建立, object = 物件, queue = 佇列, stack = 堆疊, information = 資訊, invocation = 呼叫, code = 程式碼, running = 執行, library = 函式庫, schematics = 原理圖, building = 建構, Setting up = 設定, package = 套件, video = 影片, for loop = for 迴圈, class = 類別, Concurrency = 平行處理, Transaction = 交易, Transactional = 交易式, Code Snippet = 程式碼片段, Code Generation = 程式碼產生器, Any Class = 任意類別, Scalability = 延展性, Dependency Package = 相依套件, Dependency Injection = 相依性注入, Reserved Keywords = 保留字, Metadata = Metadata, Clone = 複製, Memory = 記憶體, Built-in = 內建, Global = 全域, Compatibility = 相容性, Function = 函式, Refresh = 重新整理, document = 文件, example = 範例, demo = 展示, quality = 品質, tutorial = 指南, recipes = 秘訣, byte = 位元組, bit = 位元, context = 脈絡, tech stack = 技術堆疊, equation = 方程式, activate = 啟動、觸發, feedback = 回饋