Traditional Chinese Humanizer

Traditional Chinese Humanizer

Overview

Use this skill to turn Traditional Chinese drafts into natural, precise, Taiwan-facing writing without losing meaning. The goal is not to make text casual; it is to remove AI smell, empty polish, translationese, and unsupported claims while preserving the reader's task, evidence, and tone.

This skill is portable. It can be used by itself or loaded from OpenPress writing workflows.

Workflow

1. Identify the text's job: decision memo, proposal, product copy, report, documentation, social post, email, or article. 2. Preserve facts, claims, constraints, numbers, named entities, source attributions, and required terminology. 3. Scan for AI-writing patterns. For long or high-risk drafts, read references/ai-patterns.md. 4. Rewrite in Traditional Chinese with Taiwan usage. Read references/taiwan-style.md when the draft contains Simplified Chinese, PRC phrasing, or awkward direct translation. 5. Check evidence strength. Downgrade or remove claims that cannot be supported by the provided material. 6. Deliver the revised text first. Add a short change note only when it helps the user understand editorial decisions.

Core Rules

• Say the actual point directly. Do not use dramatic contrast to compensate for thin substance.
• Prefer concrete subjects, verbs, situations, numbers, limits, and outcomes over abstract nouns.
• Keep each paragraph responsible for one idea. A reader should know who did what, under what condition, and why it matters.
• Use active phrasing unless the actor is unknown or irrelevant.
• Avoid over-promising. Without evidence, do not write "最佳", "顛覆", "重新定義", "革命性", "前所未有", or equivalent claims.
• Trust the reader. Remove filler openings, excessive transitions, generic conclusions, and chatbot politeness.
• Vary sentence length. Use short sentences for judgments, longer sentences only when they carry real detail.
• Use Traditional Chinese and Taiwan common usage. Keep established technical terms in English when forced translation would be less clear.

High-Risk Patterns

Treat these as review triggers:

Editing Moves

1. Delete the formula: remove contrast scaffolding, generic trend openings, softening phrases, and decorative emphasis. 2. Recover the claim: identify whether the sentence is about a feature, result, risk, limitation, opinion, or next action. 3. Add missing specifics: actor, audience, scenario, data, timing, dependency, or tradeoff. 4. Match the tone: professional content can still have voice, but it should not sound like a speech, ad slogan, or chatbot reply. 5. Read aloud once. If every sentence has the same cadence, revise the rhythm.

Tables and Structured Text

Tables should scan like tables, not paragraphs.

• If the column says "規模", the cell should usually be only a number and unit.
• If the column says "狀態", avoid repeating "目前", "已經", "已支援", or "完成".
• If the column says "能力", "功能", or "備註", prefer noun phrases or short clauses.
• Move causal explanations, caveats, and evidence to the paragraph before or after the table.

Subject Continuity

Do not restart every sentence with the product, company, or founder name. Once the subject is established, continue with "產品", "平台", "團隊", "這項設計", or omit the subject when clear.

Keep the full name when:

• ambiguity would confuse the reader,
• the paragraph changes subject,
• the sentence is a conclusion that intentionally returns to the main actor.

Output Format

Default:

[revised Traditional Chinese text]

When useful:

[revised Traditional Chinese text]

修改重點：
- [specific change]
- [specific change]

Avoid long diagnostic lists unless the user asks for review details.

Final Check

• Are any slogan frames still present?
• Does each paragraph include a real subject and action?
• Are claims supported by supplied evidence?
• Is the language Traditional Chinese with Taiwan usage?
• Are English technical terms preserved when they are clearer than forced translation?
• Does the text sound like a competent person wrote it for a reader, not like a model performing polish?

AI writing patterns

Use this reference when a draft is long, public-facing, high-stakes, or visibly AI-generated. Apply judgment; do not mechanically replace every phrase if the sentence already carries precise meaning.

Empty significance

Watch for claims that inflate importance without evidence:

• 標誌著...關鍵時刻
• 彰顯...重要性
• 反映更廣泛的趨勢
• 深深植根於
• 不可磨滅的印記
• 持續演變的格局

Rewrite by naming the actual event, role, evidence, or consequence.

Before:

這次更新標誌著產品創新旅程中的重要里程碑，彰顯團隊對未來工作型態的承諾。

After:

這次更新新增批次匯入、權限分層與離線草稿，讓管理者可以先整理資料，再分批開放給團隊使用。

Promotional language

Watch for:

• 無縫, 全方位, 前所未有, 突破性, 沉浸式
• 打造, 賦能, 開啟新篇章, 重新定義
• 更智慧, 更有溫度, 極致體驗

Rewrite with product behavior, workflow effect, or measurable outcome.

Vague attribution

Avoid vague authorities unless the source is named:

• 業界專家指出
• 多份報告顯示
• 外界普遍認為
• 有觀察者表示

Use a named source, a supplied document, or remove the sentence.

Chatbot residue

Remove conversation scaffolding when it appears inside deliverable text:

• 當然可以
• 以下是...
• 希望這對你有幫助
• 如果你需要，我也可以...
• 你說得完全正確

Rewrite as the actual content.

Passive packaging

High-risk forms:

• 讓資料可以被使用
• 讓問題被看見
• 內容能被有效管理
• 這些資訊將被整合

Rewrite with an actor:

• 系統整理資料，供教師匯出成班級報表
• 後台標示逾期項目，讓管理者先處理高風險案件

Mechanical structure

Watch for:

• every paragraph ending with a short "therefore" sentence,
• every list item starting with bold labels and a colon,
• repeated three-part lists,
• repeated 此外, 然而, 值得注意的是,
• overuse of em dashes or decorative punctuation.

Rewrite by combining list items, changing sentence length, or deleting transitions that do not change meaning.

Generic conclusions

Avoid endings like:

• 未來值得期待
• 邁向更美好的明天
• 這只是開始
• 持續追求卓越

End with a concrete next step, limitation, result, or open question.

Human voice without sloppiness

Human writing can have a view. It can admit uncertainty, choose a sharper verb, or use a short sentence after a dense one. Keep that voice grounded in the material. Do not add jokes, emotional claims, or first-person phrasing unless the genre supports it.

Taiwan Traditional Chinese style

Use this reference when a draft includes Simplified Chinese, PRC phrasing, translated English structure, or mixed regional vocabulary.

Script and vocabulary

Use Traditional Chinese. Prefer Taiwan common usage when choices differ.

Translationese

Rewrite direct English structures into natural Chinese.

Technical terms

Do not force-translate terms that professional readers expect in English:

• API, OAuth, SDK, CLI
• edge case, spec, pipeline, token, prompt
• KPI, OKR, SOP

If a Chinese term is clearer and common, use Chinese:

• 採購週期
• 監考流程
• 鑑別度
• 學習歷程
• 權限控管

Use one term consistently inside the same document.

Tone

Professional Traditional Chinese should be precise before it is polished.

• Use 協助, 支援, 提供, 整理, 標示, 追蹤, 比對, 檢視, 降低, 縮短.
• Be careful with 打造, 賦能, 顛覆, 革新, 重塑, 全方位.
• Do not add idioms or literary phrasing just to sound human.
• Prefer a clear short sentence over a beautiful vague one.