chinese-content-writing-guideline

Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.

---
name: chinese-content-writing-guideline
description: >-
  Writing guidelines for producing high-quality Traditional Chinese (zh-TW) content.
  Use when writing any kind of content. Including blog posts, notes, technical articles, technical writing, chitchat, social media posts, etc., even when you are just sending a text message.
  Also use when reviewing or editing existing Chinese content for tone, style, and terminology compliance.
license: GFDL-1.3-or-later
metadata:
  author: [email protected]
---

# 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.

## 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 「我們」

## 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.

## 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

1. **Facts First**: All judgments must rest on verifiable data, case studies, or explicit logic. No vague attributions like 「研究指出」 or 「資料顯示」
2. **Direct Statement**: Prefer neutral, verifiable declarative and conditional sentences
3. **De-templated Rhythm**: Avoid mechanical three-point structures and symmetrical parallelism
4. **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.

### 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 saying things like 「我想了很久」 「我停下來想了一下」 「停下來很久」, or "being dissected" / "reading an autopsy report."
- Avoid using 「鏡子」 or related concepts to describe feelings or things. Only use 鏡子 when referring to an actual mirr