Revise

Edit prose in place without changing the author's voice or meaning. Preserve code blocks, code references, technical terms, and proper nouns exactly. If no file is given, ask which.

Two depths:

• Full revise — an article draft: steps 1–4.
• Polish only — the ask is typos, dashes, AI tells, or formatting, or the file isn't an article: step 4.

1. Context

Ask for the one takeaway the reader should remember, unless the draft already states it. Assume engineers reading a public post unless told otherwise.

2. Analyze structure

Map the sections as an information DAG — each concept depends on prior concepts. Identify dependency violations (concept used before introduced), redundant sections, missing bridges, a weak intro (hook + expectations) or weak conclusion (does it reinforce the takeaway?).

Present the current outline and a proposed reordering. Wait for confirmation before rewriting. Already well-structured → skip to step 4.