How to use the Chinese Technical Documentation Style agent skill

What the skill makes the agent do

The skill is a style guide that the agent reads and follows while it writes or reviews Chinese technical text. It is not a formatter. It does not scan or change your files on its own.

The rules cover spacing between Chinese and English or numbers, full-width punctuation in Chinese text, keeping terms such as Redis or API in English, bilingual headings, an API documentation table template, a README template, and a checklist to review a document before publishing.

• Spacing: put spaces between Chinese and English, Chinese and numbers, and numbers and units
• Punctuation: use full-width punctuation in Chinese sentences and half-width punctuation in English or code
• Terms: keep established English terms and add Chinese-English pairs on first use
• Templates: API table layout with bilingual field names, and a Chinese README structure
• Review: a checklist covering layout, terminology, content and formatting

Install the skill from the ZIP or the Claude apps

Download the ZIP for this skill from this page. The skill is in the skills/chinese-documentation folder of the jnMetaCode/superpowers-zh repository and its only listed file is SKILL.md.

To use it for all your projects, unzip it into your personal skills folder at ~/.claude/skills/. To use it for one project only, unzip it into .claude/skills/ inside that project. Make sure the skill folder contains SKILL.md.

You can also upload the skill in the Claude apps. Open Settings, go to Capabilities, then Skills, and upload it there.

Call the skill with an explicit command

This skill is set to run only when you type /chinese-documentation. The skill description says not to trigger it automatically from context, so a natural request such as 'make this README look better' will not load it on its own.

To use it, include the command in your message and then state the task. Keep the request specific, for example asking the agent to check spacing and punctuation in a named file or to draft a new API section in the template format.

• Type /chinese-documentation followed by your task
• Name the document or paste the text you want reviewed
• Say whether you want a new draft or a review against the checklist

Examples of what the agent will change

Below are examples taken from the skill's rules. The skill treats the first line as correct and the second as wrong. These show the kind of edits the agent should suggest when it applies the guide.

• Add spaces between Chinese and English: 使用 Git 进行版本管理 is correct, 使用Git进行版本管理 is not
• Add spaces between Chinese and numbers: 包含 3 个新功能 is correct, 包含3个新功能 is not
• Use full-width punctuation in Chinese: 注意：该接口需要鉴权，请先获取 Token. is correct once the punctuation is full-width
• Keep established English terms: 使用 Redis 做 Session 缓存 is correct, while translating them into Chinese is not

What the skill needs and how safe it is

The skill lists no requirements. It does not run scripts and does not use the network, according to its listing. It is a text file of rules that the agent reads.

Because it only supplies guidance, the main risk is advice that conflicts with your own style rules. Read the rules before you rely on them, and check that they match your team's conventions.

• Requires: nothing listed
• Runs scripts: no
• Uses network: no
• It does not enforce rules on files, so you still need to review the output yourself
• The skill notes that some company or publisher style guides may conflict with these conventions

Tips for getting good results

The skill works best on Chinese-heavy technical text. For documents written entirely in English, its punctuation and Chinese spacing rules do not apply.

Use the checklist at the end of the skill as a final pass before publishing. It is short and specific, so it works well for reviewing an existing document.

• Give the agent one document at a time so the review stays focused
• Ask for the API table template when you are documenting an endpoint
• Run the checklist after the agent edits a file, and check each item yourself
• If your team has its own style guide, tell the agent which rules take priority