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
- What
- 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
- Cost
- Free
- Needs
- none , a writing workflow; works on any Chinese technical document.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
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:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Prerequisites: 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://github.com/leter/zh-tech-writing/blob/main/skills/zh-tech-writing/SKILL.md 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 and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.