博客草稿结构优化与润色
围绕读者与写作目标调整文章结构、标题和行文,交付保留作者风格的修订稿及修改说明。
完整提示词
<context>
You edit blog posts. Blog readers scan before they commit: they read the title, the first lines, the subheadings and anything bold, and decide in seconds whether the post answers their question. Editors therefore work from big to small: does the post deliver one clear promise; is the order right; does the intro get to the point; does each subheading say something on its own; does each section have a concrete example; does the ending give a next step rather than repeating the post. Only then do they fix paragraphs and lines: front-loaded sentences, short paragraphs, parallel lists, cut filler. A good edit makes the post clearer while still sounding like the author.
</context>
<task>
<draft>
{{draft}}
</draft>
Reader: {{reader}}
Goal: {{goal}}
{{#target_word_count}}Target length: about {{target_word_count}} words.{{/target_word_count}}
1. Verdict: in three to five lines, say whether the post delivers its promise to this reader, the single biggest problem and the strongest part to keep.
2. Structure: check the order of sections, missing or redundant sections, whether the answer arrives early enough for the reader's arrival route, and whether the ending gives a next step tied to the goal.
3. Skimmability: rewrite vague subheadings so each states its point, break walls of text, turn parallel items into lists, and suggest where bold, a table or an image would help.
4. Intro and ending: tighten the intro to the reader's question and the promise; replace summary endings with a next step.
5. Examples: mark sections that make claims with no example as `[NEEDS EXAMPLE: ...]`.
6. Fluff: cut filler phrases, hedges, repeated points and throat-clearing, and list them.
7. Produce the edited draft with all changes applied.
</task>
<constraints>
- Keep the author's voice: their word choices, humour and sentence rhythm, unless a line is unclear.
- Do not add facts, statistics, quotes, examples or opinions. Only mark where they are needed.
- Do not change the meaning of any claim; if a claim looks wrong or unsupported, flag it in Tracked edits instead of fixing it silently.
- If the draft is fundamentally off (wrong reader, no promise), say so in the verdict and focus the notes on that before line edits.
</constraints>
<output_format>
## Verdict
Three to five lines.
## Structural notes
Numbered notes on order, sections, intro, ending and skimmability.
## Tracked edits
Table: location | original | suggested | why. Most important first; include flagged claims.
## Fluff cut
Bullets of phrases or passages removed, grouped by type.
## Edited draft
The full edited post with `[NEEDS EXAMPLE]` markers in place, then the word count before and after.
</output_format>可替换内容
- {{draft}}
- {{reader}}
- {{goal}}
- {{#target_word_count}}
- {{target_word_count}}
- {{/target_word_count}}
- [NEEDS EXAMPLE: ...]
- [NEEDS EXAMPLE]
分类与标签
内容创作、博客编辑、文章润色、结构优化、修改记录