AI writing trope review

Review the text or file the user places in scope for patterns that make prose sound formulaic, artificial, overly casual, or needlessly ornate. The target is clear writing in the author's intended voice, not a fixed “human” style. A single occurrence may be deliberate; judge repetition, clustering, context, audience, and the user's preferences.

Route the request

• For an audit or critique, report findings and examples without changing the source.
• For “rewrite”, “remove”, or an explicitly requested edit, apply only supported changes and preserve factual claims, citations, examples, terminology, code, quoted speech, and the requested language and output format.
• Do not mechanically replace every flagged word or pattern. Explain material changes when a rewrite could alter emphasis, register, attribution, or meaning. Ask when the user's desired tone is unclear.
• Do not treat a trope catalogue as a ban list. Code blocks, commands, titles, required terminology, cited quotations, and intentional rhetorical devices are excluded or reviewed separately unless the user asks otherwise.

Progressive scan

Read only the category references relevant to the text. Use the seven categories as a routing guide: