Skip to main content
skill CX Codex

personal-chinese-writing-style — Claude Code writing skill

personal-chinese-writing-style enforces one set of Chinese typography rules while the agent writes, translates or edits: quote marks, dash, ellipsis, no stray ASCII punctuation.

MIT 408 installs ★ 140 updated 2026-10-19

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sugarforever/01coder-agent-skills --skill personal-chinese-writing-style -a claude-code
Open on GitHub

What personal-chinese-writing-style does

The skill starts by sorting the job: a blog post, a translation, a subtitle file, a social post. Each type pulls its own reference — references/article-structure.md for long articles and newsletters, references/voice-and-phrasing.md for translation and editing, references/social-media-style.md for threads and short posts. references/punctuation.md is read for every Chinese output.

Punctuation is a hard requirement here, not a suggestion. Body text gets “ and ” for quotes, - with one space on each side for a dash, ...... for an ellipsis, and Chinese commas, colons and semicolons instead of Latin ones. YAML frontmatter, code blocks, inline code, URLs, file paths, shell commands and English-only sentences stay untouched.

A final pass runs before anything is returned. It catches leftover ASCII marks, a second # H1 under an existing title, and heavy endings such as a summary section or a link dump. The voice notes push toward natural Chinese tech prose and away from business jargon and self-praise lines. Point it at an English draft and nothing changes.

What it helps with

  • keep quote marks and dashes consistent across a Chinese draft
  • strip ASCII commas and periods left inside Chinese sentences
  • edit a translated article without breaking the house punctuation
  • check a long post for a duplicated H1 and a summary section
  • write a thread that ends without a filler recap

Example prompts for the agent

  • Edit this Chinese translation and run the punctuation pass before you hand it back.
  • Check the post draft: quotes “ and ”, dash -, ellipsis .......
  • Draft the article with references/article-structure.md and drop the summary block at the end.

How to install personal-chinese-writing-style

1Skills CLI (Vercel)

npx skills add sugarforever/01coder-agent-skills --skill personal-chinese-writing-style -a claude-code

2Manually: put the files in place

~/.claude/skills/personal-chinese-writing-style/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/personal-chinese-writing-style/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about personal-chinese-writing-style

How do I install personal-chinese-writing-style in Claude Code?

Run npx skills add sugarforever/01coder-agent-skills --skill personal-chinese-writing-style -a claude-code. The skill lands at ~/.claude/skills/personal-chinese-writing-style/SKILL.md.

What does personal-chinese-writing-style do?

It gives the agent a fixed set of Chinese typography and structure rules, then checks the output against them before returning it.

Which punctuation does it require?

“ and ” for quotes, - with one space per side for a dash, npx skills add sugarforever/01coder-agent-skills --skill personal-chinese-writing-style -a claude-code for an ellipsis, and Chinese sentence marks instead of ASCII ones between characters. Frontmatter, code, URLs and English sentences are exempt.

Source text

SKILL.md · MIT
---
name: personal-chinese-writing-style
description: 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.
---

# 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.

## Operating Workflow

1. Identify the content type: article/blog, translation/edit, subtitle/caption, or social post/thread.
2. Load only the needed reference:
   - `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.
3. Write or edit the content.
4. Run the final punctuation pass before delivering or saving.
5. Fix every real violation in Chinese body text, then reread the affected sentence for meaning.

## Non-Negotiable Punctuation

These are output requirements, not suggestions.

Use this exact punctuation in Chinese body text:

- Quotes: use `“` and `”`. Do not use `"` around Chinese prose.
- Dash: use ` - ` with one space on both sides. Do not use `--`, `——`, or `—`.
- Ellipsis: use `......`. Do not use `……`; do not use `...` as a Chinese ellipsis.
- Chinese sentence punctuation: use `,` `。` `:` `;` `?` `!` `、`. 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.

## Final Checklist

Before returning Chinese content, check:

- No `"` remains around Chinese body text.
- No `--`, `——`, or `—` remains as a dash in Chinese prose.
- No `……` remains; ellipsis is `......`.
- Chinese sentences use Chinese punctuation, not ASCII comma/period/colon/question/exclamation marks.
- Article prose has no duplicate body `# H1` when frontmatter already has `title`.
- Long-form article endings stay light: no `## 总结`, `## 最后`, `## 结语`, or repeated link dump unless the user explicitly asks.
- Social posts do not end with an empty self-summary such as “这是 X 的标志性时刻”.

## Voice Defaults

- Prefer natural Chinese technology prose over literal English translation.
- Avoid business cliches unless they are the precise industry term: 闭环、抓手、颗粒度、对齐、赋能、赛道、弯道超车、心智.
- Delete trust-me lines: “最干净的实现”, “每一步都是真实代码”, “最完整教程”.
- Let facts carry the point; do not over-explain the author’s conclusion in short posts.

© sugarforever · MIT · sugarforever/01coder-agent-skills

Similar skills

All skills for Writing and docs →

From the same set18

The whole set →

Project sponsors

Companies that keep this analytics open