Good morning, AI enthusiasts!
If you use AI regularly for writing emails, blog posts, or product reviews, you’ve probably built your own set of instructions: skip the filler, keep it professional, no generic openings, etc. But in most cases, these ad-hoc rules don’t stick, and your draft still opens with “In today’s rapidly evolving landscape,” uses em dashes, and reads like every other AI-generated piece on the internet. You clean it up, and the next day you start the whole process over.
After manually removing slop from every new piece of writing, rewriting AI output, and yelling at ChatGPT for 3+ years, we finally built a repeatable workflow for our team that brings consistency, removes AI slop at the prompt level, and doesn’t require you to start from scratch every time. And today I’m releasing it for free.
The Anti-Slop AI Writing Guide is a 5-page prompt template that replaces those scattered instructions with a single, structured framework.
Instead of telling the AI what to avoid and hoping it listens, the guide:
defines your structure, tone, vocabulary constraints, and accuracy rules in one prompt.
You fill in your topic and audience, paste it into any LLM, and the output follows your rules from the first draft.
It works across emails, reports, blog posts, proposals, and scripts, and requires no technical skills.
Get the Anti-Slop AI Writing Guide (Free)
The goal of this guide is not just to remove bad words from AI output. General-purpose models write in a generic voice because they have no context about who you are, how you write, or what your audience expects. The guide gives you a way to build that context into the prompt: your structure preferences, your tone, your vocabulary boundaries, your accuracy standards. Over time, this becomes a reusable persona that shapes how the model writes for you, so the gap between a first draft and your final version gets smaller with each use.
It lets you define your writing standards once, rather than editing by instinct every time. The AI follows explicit rules, not vague instructions.
The two-model workflow shifts your editing from cleanup to review. You spend time strengthening arguments and adding examples, not rewriting robotic phrasing.
It scales across teams. Anyone can use the same template and meet your standards without a style-guide walkthrough or multiple rounds of feedback.
Whether you write client-facing reports, internal documentation, or public content, the framework gives you a consistent starting point that reflects how your team actually writes. The first draft arrives closer to done, and the edits you make are about substance, not about undoing the model’s defaults.