jim60105 avatar

Chinese Content Writing Guideline

This is a comprehensive style guide for writing Traditional Chinese content aimed at Taiwan audiences. It's opinionated and detailed, covering everything from punctuation spacing (always put spaces between Chinese characters and English text) to banned phrases like "總的來說" and quotas on rhetorical devices. The author clearly wants to push back against templated, academic-sounding Chinese writing. You'd use this when writing blog posts, technical documentation, or even casual messages in zh-TW. The banned phrase list alone is worth reviewing if you write Chinese content regularly. It includes Taiwan-specific tech terminology mappings and a review checklist that enforces the rules. Fair warning, it's prescriptive to the point of rigid, but that's the point.

skills.sh installs
835
GitHub stars
22
last updated
Aug 21, 2026

Install

$ npx -y skills add jim60105/copilot-prompt --skill chinese-content-writing-guideline --agent claude-code

Installs into .claude/skills of the current project.

Files

Chinese Content Writing Guidelines

This skill provides the language-specific rules for producing high-quality 正體中文 Traditional Chinese (zh-TW) content aligned with Taiwan conventions.

Prerequisite: Always apply writing-style-guideline skill alongside this skill. That skill owns structure, tone, output principles, rhetorical device quotas, banned phrases, alternative patterns, and the general review checklist. This skill only covers what is specific to the Chinese language.

Language and Formatting

Taiwan readers parse full-width punctuation, CJK–Latin spacing, and Taiwan terminology as native; half-width commas, cramped 使用Docker, or mainland terms such as 代碼 and 函數 mark the text as converted or careless.

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

Grammar Constraints

Sponsors

Details

Repository
github.com/jim60105/copilot-prompt
Categories
Documentation, Code Review & Quality, AI & Agent Building
First seen
Jun 3, 2026

More from jim60105/copilot-prompt

All 2
1softaworks avatarbackend-to-frontend-handoff-docssoftaworks/agent-toolkitCreate API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'c821skills.sh installs
2boshu2 avatarreadmeboshu2/agentopsDraft or improve README docs.751skills.sh installs
3antithesishq avatarantithesis-documentationantithesishq/antithesis-skillsUse Antithesis documentation efficiently for product, workflow, and integration questions. Prefer the snouty docs CLI when available, and otherwise request mark644skills.sh installs
4voltagent avatarvoltagent-docs-bundlevoltagent/skillsLook up VoltAgent documentation embedded in node_modules/@voltagent/core/docs for version-matched docs. Use for API signatures, guides, and examples.613skills.sh installs
5aj-geddes avatardatabase-schema-documentationaj-geddes/useful-ai-promptsDocument database schemas, ERD diagrams, table relationships, indexes, and constraints. Use when documenting database schema, creating ERD diagrams, or writing 576skills.sh installs
6andreadellacorte avatargroove-work-docandreadellacorte/grooveCreate a 'how does X work' documentation file for a codebase component or concept. Use $ARGUMENTS as the doc topic if provided.518skills.sh installs