Make AI-assisted text sound natural

--- name: make-ai-assisted-text-sound-natural description: "Use when editing a draft that reads as machine-written: removes stock phrases, inflated claims and formulaic structure while keeping the meaning and matching the writer's own voice." --- Apply this whenever you are asked to edit, polish or make a piece of text sound more human, or when you write prose that will be published under someone's name. First, find the voice. If the person has shared earlier writing of theirs, note their sentence length, vocabulary level, how they open paragraphs and their punctuation habits, and copy those. If not, aim for a clear, direct, slightly informal professional voice. Then edit in this order: 1. Cut empty openers and closers: restating the question, scene-setting about fast-changing times, summaries that repeat the paragraph above, and closing offers of further help. 2. Replace inflated vocabulary with ordinary words. Prefer 'use' to 'leverage', 'help' to 'empower', 'important' to 'pivotal'. Remove claims of significance the text does not earn. 3. Break formulaic rhythm: everything in groups of three, 'not only X but also Y', every paragraph the same length, a bolded label at the start of each bullet. Vary sentence length on purpose. 4. Turn vague attributions ('experts say', 'studies show') into the specific source if the writer gave one; otherwise remove the claim or flag it. 5. Reduce dashes, colons and bullet lists where ordinary sentences read better. Keep headings only if the piece is long enough to need them. 6. Add specificity: a concrete example, number or detail from the writer's own material does more than any adjective. Rules: - Keep every fact, figure, name and commitment exactly as given. Never add facts or opinions the writer did not hold. - Stay within about 15 percent of the original length unless asked otherwise. - Do not swap one set of cliches for another. Return the revised text first. Then, in three bullets or fewer, list the main kinds of changes so the writer can apply them next time.

Revised: We moved the support inbox to a shared queue in May. Response times dropped from about two days to under six hours, mostly because nobody has to forward tickets anymore. The next step is tagging, so billing questions go straight to the finance team. What changed: - Removed the opener ('In an ever-evolving customer landscape...') and the closing summary. - Replaced 'leveraged a streamlined, robust solution' with what actually happened. - Merged three bolded bullets into two plain sentences and kept your figures unchanged.