write-humanly

name	write-humanly
description	Rewrite AI-sounding prose so it reads like ordinary human writing. Use for posts, comments, emails, guides, explanations, documentation, and other practical prose. Preserve the author's meaning and facts while removing repetitive AI patterns, over-structure, filler, canned transitions, and synthetic-sounding rhythm.

Human Writing

Rewrite the supplied text so it sounds like a real person wrote it.

The goal is not to beat AI detectors. The goal is readable, natural prose that preserves the author's actual meaning and voice.

Core rules

1. Preserve the facts.

   • Do not invent anecdotes, numbers, quotes, names, opinions, or experiences.
   • Do not make a weak claim stronger.
   • Do not remove technical qualifications that matter.

2. Preserve the author's intent.

   • Keep the same point, audience, and level of confidence.
   • Keep useful technical terms.
   • Do not make the text more corporate, promotional, or inspirational.

3. Prefer plain language.

   • Use common words when they are accurate.
   • Use short sentences when the idea is simple.
   • Let some sentences be longer when the thought needs it.
   • Use contractions when they fit the voice.

4. Remove unnecessary structure.

   • Do not add an introduction that only announces the topic.
   • Do not add a conclusion that repeats the post.
   • Do not turn every thought into a heading or bullet list.
   • Keep lists only when they genuinely help.

5. Keep some natural roughness.

   • Vary sentence length.
   • Vary paragraph length.
   • It is fine to start an occasional sentence with "And", "But", or "Because".
   • Do not force every paragraph into the same shape.
   • Do not polish away the author's personality.

Patterns to remove

Avoid constructions such as:

• "That's not X. That's Y."
• "Fast. Simple."
• "No fluff. Just answers."
• "Less a hammer, more a scalpel."
• "And that matters."
• "That's the part everyone misses."
• "Which is exactly the point."
• "Here's the thing."
• "Let me be clear."
• "The truth is."
• "In short..."
• "In summary..."
• "At the end of the day..."

State the actual point directly.

Do not manufacture groups of three because they sound complete. If there are two reasons, give two. If there are five, give five.

Do not invent precise numbers to sound more human.

Do not restate the whole piece at the end. End on the last useful point.

Rhythm and formatting

Avoid uniform sentence lengths and rectangular paragraphs.

Good prose can contain a very short sentence, a longer explanatory sentence, a one-sentence paragraph, and a dense paragraph where the subject needs it.

Do not deliberately insert these as a formula.

Use em dashes sparingly. Prefer commas, parentheses, colons, or periods when they read better.

Avoid decorative emoji bullets, excessive bold text, marketing-style headings, and semicolons where a period would be simpler.

Words and phrases to watch

Be suspicious of clusters of words like:

• delve
• leverage
• harness
• foster
• streamline
• showcase
• unlock
• transformative
• groundbreaking
• robust
• seamless
• nuanced
• pivotal
• crucial
• landscape
• ecosystem
• paradigm
• journey
• tapestry
• myriad
• valuable insights
• shed light on
• let's unpack
• furthermore
• moreover
• additionally

Do not replace words mechanically. Keep a term when it is the correct technical word.

Prefer ordinary alternatives when they mean the same thing:

• utilize → use
• facilitate → help or allow
• leverage → use
• commence → start
• numerous → many
• obtain → get
• regarding → about

Human markers

Natural writing often contains contractions, concrete names, real numbers, mild opinions, parenthetical asides, uneven list items, and plain verbs such as "is", "has", "uses", "gets", and "does".

Do not insert any of these artificially.

Never invent:

• personal anecdotes
• typos
• measurements
• quotes
• uncertainty
• facts

Voice preservation

If the source is casual, keep it casual.

If it is technical, keep it technical.

If it is blunt, do not make it diplomatic.

If it is restrained, do not inject jokes or slang.

Keep quirks that feel intentional. Do not correct every fragment or informal construction if it works.

Rewrite process

1. Read the whole source.
2. Identify the actual point of each paragraph.
3. Remove setup that delays the point.
4. Remove repeated versions of the same idea.
5. Replace canned phrasing with direct statements.
6. Combine slogan-like fragments where appropriate.
7. Break up sentences carrying too many clauses.
8. Restore contractions and ordinary verbs when they fit.
9. Keep concrete examples, commands, names, numbers, and technical details.
10. Remove recap endings unless they contain new information.
11. Read once for rhythm. If every sentence sounds equally polished, loosen it.
12. Compare with the source and make sure no facts or meaning changed.

Output behavior

Return only the rewritten text unless the user asks for commentary.

Do not preface it with "Sure", "Here is a more human version", or similar scaffolding.

Do not append "I hope this helps" or an offer to produce another version.

Hacker News and technical forums

Get to the technical point quickly.

Prefer concrete examples over positioning language.

Do not oversell.

Keep limitations.

A little awkwardness is better than launch-copy polish.

Do not manufacture a dramatic hook.

End with a real question only when the author actually wants that discussion.

Documentation and guides

Optimize for clarity first.

Use Simplified Technical English principles where useful:

• one main idea per sentence
• direct verbs
• concrete nouns
• short instructions
• explicit references

Do not remove necessary technical detail just to make the text shorter.

Final check

Before returning the rewrite, check:

• Did I add a fact that was not in the source?
• Did I make every paragraph too tidy?
• Did I repeat the point at the end?
• Did I use a slogan where a normal sentence would work?
• Did I add a generic hook or transition?
• Did I turn two points into three?
• Did I remove useful uncertainty or limitations?
• Does this sound like this author, or like a generic "humanized" persona?

If it sounds generic, rewrite it again using more of the source's original vocabulary and sentence structure.