write-article

Organize article

Organize the scattered content provided by the user into a fully structured Chinese article.

Step Zero: Load configuration (mandatory)

Before starting any material processing, use the Read tool to load the following configuration files in sequence (paths relative to the project root directory), and treat all rules in them as hard constraints:

1. .claude/skills/write-article/persona.md: Author persona
2. .claude/skills/write-article/style.md: Language, paragraphs, headings, numbers, regional scope
3. .claude/skills/write-article/structure.md: Chapter numbering, cases, data, connecting theory to reality, conclusion requirements
4. .claude/skills/write-article/writing-rules.md: Writing rules (append-only forbidden-zone list)
5. .claude/skills/write-article/output-format.md: Format of references and original draft appendix

Image-related (.claude/skills/write-article/references/images.md) are loaded only when the user proactively asks about images.

Step One: Collect materials

• If $ARGUMENTS contains file paths, read all specified files
• If the topic and key points are described directly, extract from $ARGUMENTS Extract
• The two can be combined
• Extract all key viewpoints, data, cases, and quotations; identify the core theme

Step Two: Analysis and planning

• Determine the core argument (summarize in one sentence)
• Group and categorize materials by logical relationships
• Design the outline: title, introduction, 3-5 core main sections, conclusion
• The outline follows structure.md 's chapter numbering specification

Step Three: Fact-checking

• Use WebSearch to verify time, data, names, and event details one by one
• When necessary, use WebFetch to retrieve authoritative sources (official websites, Wikipedia, NASA, etc.)
• Record the URLs of all cited sources
• Data in the original draft may be incorrect, proactively verify and correct it; do not copy it verbatim
• Events/policies/data from the past 6-12 months must be independently verified with WebSearch: Even if the draft gives seemingly specific claims ("approved in month X", "N million tablets", "banned on a certain date"), search again to confirm. Be especially wary of "narrative-convenient" facts in the original notes (ones that happen to fit the argument). Facts about current-affairs topics can change in the window between draft and publication
• Spot-check references: After writing the article, spot-check 1-2 key reference links to confirm that the target page really says what the main text says it says. A working URL does not mean the content matches

Step Four: Writing

Expand according to the outline while complying with the three rule sets loaded in Step Zero: persona / style / structure.

Remove repetition, merge similar viewpoints, and add necessary transitional sentences.

Step Five: Self-check

Against writing-rules.md item by itemself-check (currently 16 items), with special attention to:

• Use Grep to search ——, and confirm that the main text (excluding the original draft appendix) has zero occurrences
• Search for oily-phrasing keywords
• Paragraph length scan (2-4 sentences)
• Read through for number readability
• Regional scope consistent with the topic
• Cases have real names and data
• Popular-science articles: each theoretical concept is followed by an experimental or real-world connection
• AI-flavor scan: Grep for negative parallel sentence patterns 不是.*\(而是\|，是\)(target 0 occurrences, strict exceptions at most 1) + AI high-frequency word list in Chinese and English (crucial/significant/marks/witnesses/rooted in/delve/tapestry, etc.) + vague attribution ("generally believed" "studies show", etc.)
• Do a separate pass at the ending: additionally scan the last 3 paragraphs for the three-item progression "from.*to.*to", "prologue/new chapter/new stage", "let us/look forward together/embrace", "that image/that moment/history will remember", "the most important/the most milestone"

Whenever a violation is found, correct it immediately.

Step 6: Output

According to the output-format.md specification:

• Write to a Markdown file (project root directory)
• Append references at the end (hyperlink format)
• Append the original draft at the end (quote format, preserved as-is)
• Return to the user: file path, list of main section headings, approximate word count, number of references

Rule appending

When the user gives feedback "don't X again", append a new entry to .claude/skills/write-article/writing-rules.md (append-only, do not modify historical entries), and do not touch SKILL.md or other configuration files.