Taiwan Traditional Chinese Response Skill

TL;DR

• Mandatory Taiwanese Terminology: 元件 (component), 非同步 (asynchronous), 資料 (data), 伺服器 (server), 資料庫 (database), 快取 (cache); frameworks and code remain in English.
• Strictly Prohibited: 組件/组件 (component), 異步/异步 (asynchronous), 數據/数据 (data), 服務器/服务器 (server), 函數/函数 (function), 數組/数组 (array), 加載 (load), 依賴 (dependency)

Required Pre-Check

• Do NOT read guidelines.md before the quality check.
• Only read guidelines.md after the quality check fails, or when the user explicitly asks for a strict term audit.
• Do NOT read terms.csv before the quality check.
• Only read terms.csv after the quality check fails, or when the user explicitly asks for a strict term audit.
• Explicit audit trigger phrases (examples): "請做術語檢查" / "請做用詞審查" / "請嚴格對照 terms.csv".

Core Rules

• Use Traditional Chinese (zh-Hant-TW/zh-TW/zh_TW) with local Taiwanese terminology.
• If the user says "用中文／中文回答／中文輸出" (use Chinese/answer in Chinese/output in Chinese), it is always treated as Traditional Chinese (zh-Hant-TW) unless Simplified Chinese is explicitly specified (簡體／简体／zh-Hans／简中).
• Use Taiwanese-standard terminology (資料 (data), 元件 (component), 應用程式 (application), 資料庫 (database), 伺服器 (server)).
• Keep framework names, APIs, code symbols, and file paths in English.
• Do not turn file paths into links; use backticks directly.
• Use full-width punctuation for sentences, and half-width punctuation for code and paths.
• Wrap code and file names in backticks.

Key Terminology Cheat Sheet (Mandatory Compliance)

• component → 元件 (not "組件")
• array → 陣列 (not "數組")
• object → 物件 (not "對象")
• function → 函式 (not "函數")
• data → 資料 (not "數據")
• variable → 變數 (not "變量")
• parameter → 參數 (not "参数")
• return value → 回傳值 (not "返回值")
• import → 匯入 (not "導入")
• export → 匯出 (not "導出")
• async → 非同步 (not "異步")
• cache → 快取 (not "緩存")
• load → 載入 (not "加載")
• server → 伺服器 (not "服務器")
• database → 資料庫 (not "數據庫")
• network → 網路 (not "網絡")
• thread → 執行緒 (not "線程")
• module → 模組 (not "模塊")
• package → 套件 (not "包")
• dependency → 相依性 (not "依賴")

Quality Check and Rewriting Process

Smaller Models (Haiku, GPT-4o mini)

• Directly use the "Key Terminology Cheat Sheet" above; use the correct terminology on the first try
• No draft check process required; refer to the cheat sheet to produce correct output directly
• Only read guidelines.md and terms.csv when the user explicitly requests a term audit (e.g., "請做術語檢查")

Larger Models (Sonnet, Opus, GPT-4)

1. First produce a draft, then perform a quality check
2. If any terms from the "Strictly Prohibited" list above appear, it is considered a failure
3. Passed quality check: Do not open guidelines.md and terms.csv
4. Failed quality check: Read guidelines.md and terms.csv for strict term audit and rewrite
5. Only provide the passed version in the final output; do not mention the check or rewriting process

Minimal Example

Use React, load data in `useEffect()`.
The file is located at `src/components/Button.tsx`.

Quick Checklist

• Traditional Chinese (zh-Hant-TW)
• Refer to the Key Terminology Cheat Sheet (mandatory for Haiku/small models)
• No prohibited terms (組件, 異步, 數據, 服務器, etc.)
• Taiwanese terminology (元件, 非同步, 資料, 伺服器)
• English proper nouns retained (React, useState, API)
• Full-width punctuation for sentences, half-width punctuation for code
• Code and file names wrapped in backticks

References

• Key Terminology Cheat Sheet - Mandatory for small models ⭐
• guidelines.md - Complete guide (for large models or explicit audits)
• terms.csv - Terminology comparison table (460+ entries)
• Wikibooks Comparison Table - CC BY-SA 4.0
• Ministry of Education Revised Chinese Dictionary