Subscribe
paid-only post openai

My Exact OpenAI Prompt For Blog Posts That Don’t Sound Like AI

After three months of abusing GPT to write my blog, I ended up with a very opinionated system prompt. Here is the exact prompt, the banned phrases, the structure rules, and what actually mattered.
Richard Lemon

by Richard Lemon

My Exact OpenAI Prompt For Blog Posts That Don’t Sound Like AI
Photo by Compagnons / Unsplash

Why I Started Treating GPT Like A Junior Ghostwriter

I write a lot, but I do not always feel like typing a lot.

So I started using GPT as a sort of junior ghostwriter for my blog on richardlemon.com. Not to "create content". To keep my publishing cadence up while I am busy shipping weird web experiments and coaching baseball.

The problem: every unconfigured model sounds the same. Smooth. Bland. Corporate. Like it just finished a LinkedIn course on "thought leadership".

So for three months I iterated on a single system prompt. Same idea. Lots of small edits. My goal was simple. Posts that still sound like me after the AI takes a pass at the keyboard.

This post is the current state of that system prompt. The exact text. The banned phrases. The structure rules. Plus what actually moved the needle.

This post is for paying subscribers only

Subscribe to continue reading

Similar topics

The Make.com Modules I Actually Use Every Week (And The Ones I Killed)

The Make.com Modules I Actually Use Every Week (And The Ones I Killed) →

I spent a few weekends brutally auditing my Make.com scenarios. These are the modules that actually earn their place every week, and the ones I ripped out as pure complexity.
Featured
My Full Make.com Blueprint For Automating a Sheets → OpenAI → Ghost Content Pipeline
Featured

My Full Make.com Blueprint For Automating a Sheets → OpenAI → Ghost Content Pipeline →

I wired my entire content pipeline into Make.com so a single row in Google Sheets turns into a published Ghost post. Here is the exact scenario, module by module.
Why I Still Rely On Tower For Git In The Era Of AI Coding

Why I Still Rely On Tower For Git In The Era Of AI Coding →

AI tools can write the CSS and scaffold components, but they do not own my Git history. I still rely on Tower because visual Git control is non-negotiable.