Chinese Technical Writing Guide , strip AI tone, enforce typography rules
Style rules for Chinese technical docs (READMEs, design docs, API references, tutorials): short plain sentences, colleague tone, facts over adjectives, an AI-tone checklist to run against every draft, strict CJK typography
Curated by Skill Harbor: style rules for writing Chinese technical documentation that reads like a senior engineer wrote it: plain, concrete, short sentences. One idea per sentence, active voice, facts instead of adjectives ("p99 latency dropped from 120 ms to 40 ms", not "performance greatly improved"), paragraphs that open with their point, and strict CJK typography (full-width punctuation, spacing between CJK and Latin, correct quotes and ellipses). The heart of it is an AI-tone checklist to run line by line against every draft: kill the stock openers and closers, the "not A but B" contrasts, the triple adjectives, the hype words, the jargon. by @leter, listed here with credit to its creator. Honest caveats: the skill content is written in Chinese and targets Chinese-language docs; also ships a typography reference and a manual-structure reference to read when those topics come up. Skill Harbor never reviews the code, review it yourself before use. Discovered via GitHub.
Version:
Quick answer
This guide, by leter, sets the style rules for Chinese technical documentation — READMEs, design docs, API references, tutorials — that reads like a senior engineer wrote it. Short plain sentences, facts over adjectives, strict CJK typography, and an AI-tone checklist to run against every draft.
At a glance
| What it is | A writing-rules skill for Chinese-language technical documents: sentence and paragraph discipline, a colleague tone, and a line-by-line checklist that strips out stock AI phrasing. The skill's own content is written in Chinese. |
|---|---|
| Who it's for | Writers and engineers who produce technical documentation in Chinese and want it concrete and human-sounding instead of padded and generic. |
| What you give it | A Chinese technical document or draft to write or revise. No prerequisites — it works on any Chinese technical document. |
| What you get | Drafts and revisions that follow the rules: one idea per sentence, active voice, numbers instead of hype adjectives, paragraphs that open with their point, and correct full-width punctuation and CJK/Latin spacing — plus a typography reference and a manual-structure reference. |
| Works with | Muse, installed from this page with the copy-paste install prompt, applied to your Chinese writing workflow. |
| Cost | Free |
| Time | A few minutes to install. Revising a document is one pass: draft, checklist, typography. |
Example — tightening a Chinese API doc paragraph
An example of the revision pass the guide prescribes, described in its own terms:
- You hand over a draft paragraph of a Chinese API reference that claims a change made the service much faster, in vague terms.
- The checklist pass cuts the stock phrasing and the hype adjectives, splits the long sentences to one idea each, and replaces the vague claim with the concrete fact the guide demands — the kind of sentence that states the before and after numbers.
- A final typography pass fixes the CJK details: full-width punctuation, spacing between Chinese characters and Latin words or numbers, and the correct quotes and ellipses.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit ffda935Prerequisites: none , a writing workflow; works on any Chinese technical document. Install "Chinese Technical Writing Guide , strip AI tone, enforce typography rules" for me. It gives my agent @leter's style rules for Chinese technical docs: short plain sentences, colleague tone, facts over adjectives, paragraph and heading structure, strict CJK typography, plus an AI-tone checklist to run against every draft. Note: the skill text is in Chinese and targets Chinese-language documentation. Repository: https://raw.githubusercontent.com/leter/zh-tech-writing/ffda9353768dece8aabd26ccb3a4978025e9437c/skills/zh-tech-writing/SKILL.md Pinned version: install the code at commit ffda9353768dece8aabd26ccb3a4978025e9437c exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files, including the typography and manual-structure references) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "zh-tech-writing". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing technical , point it at a Chinese doc to write or revise). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- ffda935 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.