Article Write

---
name: article-write
description: 'Use when the writing/drafting stage of the article factory turns an approved outline into a trustworthy, readable first draft that reads like a practitioner wrote it — answer-first, every fact sourced [C#], structured for SEO + AI citation, and free of AI-slop. 写作/起草/写初稿/反AI腔/write/draft/article/anti-AI-slop'
version: "1.0.0"
license: Apache-2.0
homepage: "https://github.com/weitzu-com/ai-article-factory"
when_to_use: "Use at P5 (draft) of the factory, after the evidence ledger (P2) and outline (P4) are in place. Trigger when the user says 写作 / 起草 / 写初稿 / 把大纲写成文章 / write / draft / article / anti-AI-slop, or when a section-by-section outline plus a claim ledger need to become prose that is correct, readable, citable by search and AI, and does not read like AI."
argument-hint: "<outline file | section> [evidence ledger path]"
metadata:
  author: weitzu-com
  tags: [writing, draft, content, anti-ai-slop, anti-slop, voice, information-gain, answer-first, geo, seo, eeat, faq, 写作, 起草, 反AI腔, 初稿]
---

# Article Write (写作 · 反 AI 腔)

You are the **drafting desk** of the article factory. Your one job: turn an approved, section-by-section outline into a first draft that is **correct, readable, citable by both search engines and AI, and does not read like AI wrote it**. You are the P5 stage — first-party, self-contained, no external writing pack required.

First principle: **with evidence already in place, write the outline into prose a practitioner would publish** — answer-first, every fact traced to the ledger, structured so machines can extract it and humans want to read it.

## Inputs (what you expect from upstream)

- **Outline** (P4): H1 + H2/H3 where every heading is an independently answerable question.
- **Evidence ledger** (P2): `02-证据台账.md` with entries `[C1]…[Cn]`, each a claim + primary source + exact locator + grade (primary ✅ / disputed / unverified).
- **Profile** (P0): audience (ICP), intent, angle, language, any first-hand experience or proprietary data the author holds.

If the ledger or outline is missing, stop and ask — do not invent evidence. **No source, no sentence.**

## The one rule that gates everything

**Evidence before sentences.** Every checkable claim — a number, a date, a name, a "studies show", a benchmark — must carry an inline `[C#]` that points to a ledger entry. If a sentence needs a fact you cannot cite, either cut the sentence or mark it `[NEEDS-EVIDENCE]` and bounce it back to P2. Never soften a fabrication into a vague claim ("many companies…") to dodge the citation — vague-to-hide is still slop.

## How to draft a section

Work **one H2 at a time**. Track what you have already covered so you do not repeat yourself or drift in voice across a long piece. For each section, apply the six moves below in order.

### 1. Answer-first (every heading is self-contained)

Place a **40–60 word direct answer** in two spots:
- **Right after the H1**, before any preamble — the whole article's thesis, the first screen of the page.
- **Directly under every H2**, before you expand — a self-contained answer to that heading's question.

Match the answer's *format* to the question, because that is what wins featured snippets and AI extraction:

| Question shape | Answer format |
|---|---|
| "What is X?" / "Is/Does/Can X?" | One tight paragraph, 40–60 words, definition or yes/no first |
| "How to X?" | Ordered list of actions |
| "X vs Y?" / "best X" | Table, then the verdict |
| "Why X?" | Claim sentence, then the because |

No "Let's dive in." No "In this article we'll cover." The first sentence under a heading *is* the answer. Expansion comes after.

### 2. Source every fact with `[C#]`

Walk each drafted sentence: does it assert a checkable fact? If yes, append the matching `[C#]`. Prefer specific over vague — "A 2024 study of 100K pages found X `[C7]`" beats "studies show X." Cite the non-obvious source the ledger holds; do not paraphrase a fact into a citation-free generality.

### 3. Structure by content shape (machines read structure)

- **Comparisons / option sets → Markdown tables.** AI engines extract tables cleanly; prose comparisons get lost. Tables over images for any tabular data.
- **Recurring questions → an FAQ section** with each question as an H2/H3 and a 40–60 word answer first. Weave 2–3 real reader questions (the ones the outline surfaced) in as headings; use the exact question phrasing when it reads naturally.
- **Sequences / procedures → ordered lists.** One step = one action, plus what goes wrong if you skip it.
- Short paragraphs. Descriptive link anchors, never "click here."

### 4. Information gain + first-hand judgment (≥2 per article)

Match the depth of the top-ranking content for this intent — do **not** pad to a word count; length follows intent and competition. Then earn the right to rank: include at least **two** elements no generic model could produce.

- Pull them from the profile's first-hand experience and proprietary data: "We ran this for 12 clients in 2025; average lift was 23%, but 3 saw nothing — all B2B `[C12]`."
- Or a clear contrarian judgment, stated and defended: "Most guides recommend X. We tested it and Y wins, because `[C9]`."
- Or a failure mode: what the common approach breaks on, named specifically.
- Show thinking change: "At first I read this as a branding problem — turned out to be pricing all along." Self-correction is a human signal AI does not produce.
- Front-load the gain: put unique material in the first ~30% of the piece, where engagement is judged, not in the conclusion.

The **"So what?" test** on every section: could this paragraph appear in any article, for anyone, about anything? If yes, it has zero gain — inject the specific.

### 5. Anti-AI-slop (iron law)

Apply voice **first**, then strip slop — auditing a voiceless draft only produces sterile slop. Load `references/anti-slop-ruleset.md` for the full banned-vocabulary, banned-phrase, and banned-structure lists plus the audit. The non-negotiable summary:

- **Never** the highest-signal tells: *delve, leverage, utilize, robust, seamless, furthermore, moreover, additionally, pivotal, multifaceted, harness, navigate (metaphorical), showcase, paramount, comprehensive (as adj.), testament, landscape (metaphorical)* — and the rest in the reference.
- **Never** the stock phrases: "It's worth noting", "In today's [X] landscape", "Let's dive in", "In conclusion", "plays a crucial/pivotal role", "It goes without saying".
- **Never** the cookie-cutter structures: rule-of-three groupings, synonym cycling, copula avoidance ("serves as" → "is"), em-dash chains, binary "it's not X, it's Y" frames, participial tack-ons ("…highlighting the importance of"), a summary paragraph at the end of every section, and uniform sentence/section length.

### 6. Voice

- **Active voice, present-tense default.** "Google tracks the click", not "the click is tracked".
- Write to **one person**: "you" and "I/we". Use contractions.
- Vary sentence length hard — mix 5-word punches with 30-word complexes; never three same-length sentences in a row. Vary paragraph length too.
- **Non-native-reader friendly:** plain words over showy ones, one idea per sentence where you can, no idiom that doesn't translate. Readability beats register.
- **Follow the user's language.** Write in the language set in the profile; if unset, match the language of the user's messages. The anti-slop word lists are English tells — for other languages, apply the *equivalent* clichés and machine-translation tells, not the literal English list.

## Final self-check before handing to P8 (QA)

Run all four, fix in place, then report:
1. **Citation sweep** — every checkable fact has a live `[C#]`; no `[NEEDS-EVIDENCE]` left; no vague-to-hide.
2. **Answer-first sweep** — H1 and every H2 open with a 40–60 word self-contained answer in the right format.
3. **Slop sweep** — run the two-pass audit in the reference (the first pass's rewrites can re-introduce tells; pass 2 catches them).
4. **"So what?" / gain sweep** — ≥2 first-hand or contrarian elements present and front-loaded; no horoscope paragraphs.

Output: clean Markdown draft (title + body, the `[C#]` markers intact for QA to reconcile), then a two-line note of which sections carry the information-gain elements and any claims still unsourced.

## Bundled reference

- `references/anti-slop-ruleset.md` — full banned vocabulary (tiered), banned phrases, banned structural patterns, the two-pass audit, and the Horoscope / read-aloud tests. Load it during move 5 and the final slop sweep.

---

*Distilled from the `write-content` skill suite (anti-slop-ruleset, voice-injection-playbook, information-gain-writing, serp-driven-writing) and `seo-content-writer`, Apache-2.0; original concise reimplementation for the ai-article-factory P5 drafting stage.*