writing-assistant

Writing Assistant

Writing Assistant, two modes:Idea Guidance(write from scratch) andReview and Polish(revise an existing article).

Prerequisites

Tool	Type	Required	Installation Method
markdownlint-cli2	CLI	No	npx markdownlint-cli2, no installation required, used for review step 6
markdown-lint	skill	No	Optional, provided by an independent developer-workflows plugin

Do not proactively check these tools when loading the skill. When a command fails due to a missing tool, then guide the user step by step through installation and configuration.

Mode Selection

User Intent	Mode	Section
"Don't know what to write," "help me brainstorm," "write a travelogue," "record a TIL," "write something"	Idea	Idea Mode
"Help me revise my article," "take a look," "polish," "proofread," "look at the article"	Review	Review Mode

When the intent is unclear, ask the user first.

Idea Mode

Help users who do not know what to write or how to continue by guiding their writing through heuristic questions.

Core Principles

Principle	Description
One question at a time	First design a list of questions, then ask them one by one
Continue after confirmation	User thinks → writes → revises → confirms → next question
Inspire rather than ghostwrite	Use questions to stimulate thinking, do not decide the content direction for the user

Article Type Determination

User Intent	Type	Framework
"Write a travelogue," "record a trip"	Travelogue	Departure → Journey → Looking Back
"Record a TIL," "learned today"	TIL	Background → Process → Solution → Takeaways
"Write something," "help me brainstorm"	General Article	Trigger → Viewpoint → Development → Conclusion

Process

判断文章类型 → 列出引导问题 → 逐个提问 → 用户回答 → 确认 → 下一题 → 整理成文

Questioning Rhythm

Claude: "Why did you want to visit this place?"
User: [writes answer]
Claude: [confirm/follow-up] -> "OK, next question: what was the first thing you saw when you arrived?"

Writing Framework

Each type has a corresponding article structure and guiding questions. See the full content in writing-frameworks.md。

After the draft is complete, it is recommended to switch to Review Mode.

Review Mode

Article review, providing a 6-step review process to help polish Chinese articles.

Core Principles

Principle	Description
Discuss before revising	Offer revision suggestions for the user to choose from, do not change directly
Review by section	Use Markdown headings as checkpoints, handling 1–2 sections at a time
Inspire rather than decide	Use questions to guide the content, and do not make decisions for the user

Six-step review process

1. 结构 → 2. 读者语境 → 3. 语言 → 4. 来源核验 → 5. 风格 → 6. Markdown 格式

Step 1: Structural diagnosis

Goal: Ensure the structure is clear and the topic is focused.

• Split paragraphs and identify topics.
• Propose 2–3 reorganization options,discuss before revising。
• Move deleted content into a separate material.md file.

See structure-review.md。

Step 2: Reader context check

Core question: "Will the reader be confused here?"

Issue	Manifestation	Handling
Assumed background	Using terms or abbreviations without explanation	Add explanation or footnote
Self-reference	Using "like that..." without explaining	Change to a specific description
Logical leap	Jumping directly from A to C	Add transitional explanation
Emotion lacks setup	Using "really too..." without context	Add background first
Information gap	Assuming the reader knows the causes and consequences	Briefly add background

See structure-review.md。

Step 3: Language standards

Refer to Yu Guangzhong's "How to Improve English-style Chinese?":

Issue	Example
Abstract noun as subject	Bad: The decrease in income changed life → Good: He changed his life because his income decreased
Wordy expression	Bad: Based on this reason → Good: Therefore
Weak verb	Bad: make a contribution → Good: contribute
Preposition stacking	Reduce excessive use of connectives
Overuse of passive voice	Bad: The problem was solved → Good: The problem is solved

See chinese-style.md。

Step 4: Source verification

Source priority: Official government sources > authoritative media > industry media > avoid personal blogs as much as possible.

Rhythm: Verify one item → discuss → write one item → confirm → next item.

See source-verification.md。

Step 5: Style consistency

Check according to personal writing style:

Check item	Description
Signature expressions	"How should I put it," "actually," "a bit..."
Tone	Self-deprecating opening, parenthetical comments
Quantification	Use specific numbers to enhance persuasiveness
Restrained bolding	Bold at most 3 places per heading section

Avoid:

• The "not X... but Y..." sentence pattern, which has obvious AI traces.
• Using quotation-mark-wrapped "humorous" metaphors.
• Opening with Emoji or a numbered list.
• Frequent use of dashes.
• Using --- horizontal dividers; use headings or numbers for natural transitions instead.

See personal-style.md。

Step 6: Markdown formatting

npx markdownlint-cli2 article.md          # Check
npx markdownlint-cli2 --fix article.md    # Auto-fix

Additional manual checks:

• Heading levels are reasonable, with no skipped levels between H2 and H3.
• List formatting is consistent, uniformly using - or *。
• Code blocks have language tags.

Review cadence

1. 读取当前章节。
2. 按六个步骤检查。
3. 提出建议，不直接修改。
4. 等待用户确认。
5. 确认后进入下一章节。

Key rule: After each chapter is reviewed, wait for user confirmation.

Writing style quick reference

Element	Requirement
Language	Conversational, like talking with a friend
Paragraphs	Each paragraph expresses only one topic
Bold	Use only for important turns and viewpoints, at most 3 places per section
Data	Integrate into the narrative of experiences, put detailed sources in footnotes
Honesty	Acknowledge information gaps, mark unfinished content, preserve the thinking process

Detailed reference

• writing-frameworks.md: Ideation framework for travelogues, TILs, and general articles
• chinese-style.md: Chinese language conventions
• structure-review.md: Structural diagnosis and reader context
• source-verification.md: Source verification and footnotes
• personal-style.md: Personal style guide