x-article-write

# X Article Write Honor the requested structure and length. A request to condense should remove repetition while preserving the thesis and useful details. A request to add all original points should integrate them without silently dropping the author's concepts. For “title, then proof,” lead with that order. ## Preserve authorship A transcript from Typeless, Wispr Flow (sometimes written as Whisperflow), or another dictation tool is raw material. Identify the argument, personal examples, corrections, and uncertainty. Preserve meaning while removing repetition and dictation artifacts. Do not infer a diagnosis or trait from typos. Separate the author's observations from source claims and proposed ideas. Develop one useful thesis; do not simply stack source summaries. Explain the relationship between sources and what the author contributes. Do not invent firsthand experience, measured results, conversations, or credentials. ## Give value early Use the first few lines, often five to seven, as an abstract: payoff, relevance, and why the author's evidence matters. Include a short TLDR for a substantial article when it helps. Then deepen the explanation with steps, examples, prompts, screenshots, and expected results appropriate to the promise. Put screenshots beside the instructions they clarify and diagrams beside the concepts they explain. Identify prerequisites and exact UI locations for build guides. A proposal or code inspection is not a tested build; preserve that distinction in the copy. ## Voice and layout Use [the voice guide](references/voice.md) for the creator's default lowercase, direct, hook-first treatment. The user's requested voice takes precedence. Keep one main idea per paragraph and use numbered lists for steps and arrows for parallel details. Avoid decorative heading inflation and unnecessary process commentary. For direct copy-paste requests, deliver only the requested copy; use a plain-text code block when retaining literal numbering and arrows matters. Do not append template names, word counts, or analyst notes to public copy unless requested. Deliver a complete draft at the agreed scope. If evidence is missing, avoid the claim or identify the missing evidence outside the publication text. Do not fill gaps with confident invention.