Overview
4-step workflow: search for materials → write the article → generate titles → formatting optimization. Suitable for platforms such as WeChat Official Account, Zhihu, and Juejin.REQUIRED： Apply Chinese punctuation conventions throughout the full text (see the format section in Step 2).
When to Use
- Write WeChat Official Account articles, Zhihu technical articles, self-media content
- Rewrite and publish based on existing technical documentation
- Need viral titles, formatting suggestions, multi-platform adaptation
When NOT to use： Pure academic papers (use ml-paper-writing), fiction writing (use writer-memory), in-project documentation (use doc-coauthoring)
Preparation Before Execution
- Read project context (CLAUDE.md, AGENTS.md, etc., if present) — writing style, closing remarks
- Read source materials (if specified) — existing documents, technical materials
- Confirm the target platform — WeChat Official Account/Zhihu/Juejin, with slight differences in word count
Key Actions: You must first read the project context, then read the source materials, and finally confirm the target platform.
Step 1: Search for Materials
When the topic needs supplementation, use WebSearch: parallel multi-source, prioritize the latest, in-depth summarization. If the user has already provided complete source materials, this can be skipped.
Step 2: Write the Article
Structural Templates (choose by type)
| Type | Framework |
|---|---|
| Technical Popular Science | Popular science → case study → summary |
| Principle Analysis | Surface phenomenon → in-depth analysis → conclusion |
| Usage Tutorial | Effect demonstration → step-by-step teaching → elevation |
| Tool Review | Introduction → usage process → review conclusion |
General Structure: Effect demonstration → problem description → step-by-step teaching → elevation and summary
Writing Requirements
- 1000–1500 words; story-style opening or directly hitting the pain point; 2–3 alternative titles
- Principles: specific, easy to implement, visibly effective (executable steps, with comparisons and data)
Format
Chinese Punctuation Conventions(strictly follow throughout the full text):
| Punctuation | Use | Do Not Use |
|---|---|---|
| Comma | ， |
, |
| Period | 。 |
. |
| Semicolon | ； |
; |
| Colon | ： |
: |
| Question mark | ？ |
? |
| Exclamation mark | ！ |
! |
| Parentheses | （） |
() |
| Book title marks | 《》 |
- |
Exceptions (keep the original text): technical terms (JavaScript, React, etc.), code/commands, URLs/paths, version numbers/numbers. English punctuation within book title marks may be retained (e.g., 《JavaScript: The Good Parts》).
Leave blank space before and after code blocks, with syntax highlighting.
Step 3: Generate Titles
Generate 5 titles, with elements: clear pain point, attractive numbers, result-oriented, emotional appeal, suspense setup.
| Element | Example |
|---|---|
| Pain point | "Still switching Node manually?" |
| Numbers | "3 minutes" "5 tips" |
| Result | "Efficiency skyrockets 10x" |
Optional Vibe Coding format:《Vibe Coding 10X 提效：[成果]，[痛点]》
Step 4: Formatting optimization
- Paragraphs: 3–5 lines per paragraph, bold important data, standalone paragraphs for key quotes
- Images: cover under the title, effect images after steps, CTA at the end
- Code blocks: leave whitespace before and after, syntax highlighting
- Ensure paragraph length is between 3–5 lines for easy mobile reading
Quick Reference
| Stage | Key actions |
|---|---|
| Preparation | Read project context, source materials, confirm platform |
| Search | WebSearch when supplementation is needed; can be skipped if source materials are available |
| Writing | Choose a structure template, 1000–1500 characters, Chinese punctuation standards |
| Titles | 5, including pain points/numbers/results |
| Formatting | 3–5 lines/paragraph, image placement, code whitespace |
Common Mistakes
| Mistake | Correction |
|---|---|
| Skipping project context | Read first, then write, maintain consistent style |
| Ignoring Chinese punctuation standards | Chinese punctuation and terminology standards must be used |
| Vague titles | Must include pain points or numbers or results |
| Still searching extensively when source materials are available | Prioritize source materials, only supplement and verify |
With Skill
| Skill | Function |
|---|---|
| wechatsync | Multi-platform synchronization |
| doc-coauthoring | Structural refinement, reader testing |