Apply the user's Chinese writing style when writing, translating, editing, proofreading, polishing, or publishing Chinese content, including blog posts, articles, subtitles, captions, tweets/X posts, threads, newsletters, and social posts. Enforce punctuation rules, especially Chinese curved quotes, halfwidth dash " - ", ASCII ellipsis "......", and no leftover fullwidth/English punctuation in Chinese body text.
npx skills add https://github.com/sugarforever/01coder-agent-skills --skill personal-chinese-writing-style
Use this skill for Chinese content. The goal is not to explain the style back to the user; the goal is to apply it and verify the final text.
references/punctuation.md - always read for Chinese output.references/article-structure.md - read for blog posts, newsletters, long articles, and technical writeups.references/voice-and-phrasing.md - read for translation, editing, and long-form Chinese prose.references/social-media-style.md - read for X/Twitter, threads, short social posts, and launch notes.These are output requirements, not suggestions.
Use this exact punctuation in Chinese body text:
“ and ”. Do not use " around Chinese prose. - with one space on both sides. Do not use --, ——, or —........ Do not use ……; do not use ... as a Chinese ellipsis., 。 : ; ? ! 、. Do not leave , . : ; ? ! between Chinese characters.Allowed exceptions: YAML frontmatter, code blocks, inline code, JSON/config, URLs, file paths, shell commands, exact source quotes, and English-only sentences.
Before returning Chinese content, check:
" remains around Chinese body text.--, ——, or — remains as a dash in Chinese prose.…… remains; ellipsis is .......# H1 when frontmatter already has title.## 总结, ## 最后, ## 结语, or repeated link dump unless the user explicitly asks.Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take sugarforever/personal-chinese-writing-style from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.