chinese-documentation

Applies Chinese technical writing conventions for spacing, punctuation, terminology, and document structure.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/bill80362/laravel-thread-admin --skill chinese-documentation-bill80362
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chinese-documentation
Source: https://github.com/bill80362/laravel-thread-admin/tree/main/.github/superpowers/chinese-documentation
Command: npx skills add https://github.com/bill80362/laravel-thread-admin --skill chinese-documentation-bill80362

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Chinese technical documents often read awkwardly due to missing spaces between Chinese and English text, mixed full-width and half-width punctuation, machine-translation tone, and inconsistent terminology. This Skill provides a complete set of Chinese technical writing conventions so documentation reads naturally and stays consistent. ## Core Features & Use Cases - Typography Rules: Enforces spacing between Chinese/English text and numbers, correct full-width vs half-width punctuation, and proper bracket and quotation mark usage. - Terminology Guidance: Defines when to keep English terms (React, API, Redis) versus translate them, with first-occurrence bilingual annotation conventions. - Ready-Made Templates: Provides bilingual API documentation templates and a Chinese README.md structure for open-source projects. - Use Case: When writing a Chinese README or API reference for an open-source project, apply these rules to avoid mixed punctuation, cramped CJK-Latin text, and translation awkwardness, then verify with the included pre-publish checklist. ## Quick Start Use the chinese-documentation skill to review and rewrite my Chinese README following standard Chinese copywriting typography conventions.

Frequently Asked Questions about chinese-documentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I format mixed Chinese and English text in technical documentation?

Add a space between Chinese characters and English words or numbers, such as "使用 Git 进行版本管理". Do not add spaces around full-width punctuation, and keep degree and percent signs attached to numbers like 95%.

What are the Chinese copywriting guidelines for punctuation?

Use full-width punctuation (,。:) in Chinese sentences and half-width punctuation in English or code contexts. Use full-width parentheses for Chinese content and half-width parentheses when the enclosed content is English or numeric.

Should technical terms be translated into Chinese in documentation?

Keep widely used terms like API, Redis, Kubernetes, and middleware in English, since forced translations reduce clarity. Translate concepts with established Chinese equivalents like 数据库 or 版本控制, and annotate terms bilingually on first occurrence.

How do I avoid machine-translation tone in Chinese technical writing?

Replace passive constructions like "被用来" with direct phrasing like "用于", remove redundant pronouns, and split long European-style sentences into short statements. Organize dense paragraphs into lists and tables.

When should this Chinese documentation skill be triggered?

It is designed for explicit invocation via /chinese-documentation only, not automatic triggering from context. Use it when writing or reviewing Chinese technical documents, READMEs, or bilingual API references.