Turns Out The Fix Wasn’t In The Prompt At All

A redditor over on r/PromptEngineering, u/Hrolgarr, tried the move we’ve all tried: a long style section, a banned-words list, “write casually.” Worked for a draft or two, then the AI-voice crept right back in. What’s new is where he moved the fix. Not inside the prompt. Outside it, into two small systems that run on every draft.

Here’s the twist, and it’s a good one: he didn’t just ban AI tells, he calibrated the checker against his own 163 sent messages and threw out any rule that flagged more than a quarter of his own writing. Because a rule that fires on your own normal sentences isn’t catching the model, it’s catching you. That’s the part most people skip when they build a linter for “sounding human.”

The mini workflow, as he’s running it:

  1. Every time he edits or tosses a draft, the before/after gets logged 📝
  2. Once a night, a model reads those pairs and writes specific rules (lists of three, “it isn’t X, it’s Y,” same-length paragraphs, the end-of-message recap, all flagged)
  3. Capped at six new rules a night, 25 total, plain text, easy to delete
  4. Those rules load into the next draft’s context before he ever sees it
  5. The checker runs first and blocks banned words and structural tells on the spot 🔍

Pro tip: general advice does nothing. “Be concise” changes zero output. “Don’t list the work already agreed, keep only the new point” changes everything, because it’s a rule the model can actually execute. And the community thread backs this up too, more than one commenter said their own list ended up short and mostly about how a draft ends, since that’s where the model wants to summarize itself back into AI-land.

If you’re fighting the same drift in your own prompts, go read his write-up, there’s a before/after you’ll want to see: https://hrolgar.com/blog/a-linter-for-text-that-sounds-like-ai?utm_source=reddit&utm_medium=social&utm_campaign=ai-linter-promptengineering ⚓️

Frequently Asked Questions

Q: Why don’t general prompt rules like “be concise” or “sound natural” actually work?

General instructions get overridden as conversations go on. What changed the game was specificity. “Don’t list the work already agreed, keep only the new point” actually shifted output. “Be concise” doesn’t. The model needs operational rules, not vibes.

Q: What specific rules actually moved the needle?

Endings (no recap, stop on a concrete point instead of a soft offer), paragraph length consistency (the model tends to make them all the same length, which reads generated), and structure catches (flagging lists of three, repetitive sentence patterns). These showed up across multiple commenters’ workflows as real change-makers.

Q: When you calibrate your checker on your own messages, how do you avoid just measuring your own style?

Drop any rule that flags more than 25% of your sent messages. If a rule catches you that often, it’s measuring you, not the model’s drift. This keeps the checker from becoming a generic blandness filter.

Q: Should I put these rules in the prompt or build them as external checks?

External checks worked better across the board. Prompts shape initial direction, but a post-processor running before you see the draft actually enforces the rules. Prompt instructions alone get overridden in longer conversations.

“Don’t sound like AI” in the prompt didn’t work for me. Rules learned from my own edits did.
by u/Hrolgarr in PromptEngineering

Scroll to Top