Make your whole blog follow one style guide

If more than one person has ever written for your blog — or if you simply wrote differently two years ago than you do now — your archive is inconsistent in small, persistent ways. Oxford commas here and not there, “ebook” and “e-book” and “eBook”, headings in title case on some posts and sentence case on others, em dashes spaced one way in old posts and another in new ones. Individually trivial; collectively, it reads as unmaintained. A style guide only helps if it is actually applied, and applying one across hundreds of existing posts by hand is not realistic. As a recipe across the whole connected archive, it is.

Codify the rules, then apply them

Specter connects to your Ghost blog in the browser and brings every post into one workspace, so the whole archive is content an AI recipe can work through at once. The first move is to write your rules down plainly — that’s your style guide, and it doubles as the recipe. Be concrete; vague rules produce vague edits:

Apply these style rules to every post. Change only what violates a rule; leave everything else, including meaning and voice, exactly as it is:

• Use the Oxford comma.
• Headings in sentence case, not title case.
• “email” not “e-mail”; “website” not “web site”.
• Spell out numbers under ten; numerals for ten and above.
• One space after periods.

Make no other changes.

The instruction to change only rule violations is the important part. You’re normalizing mechanics, not rewriting prose — a style pass that “improves” your sentences is a different, riskier job you’d scope as a separate recipe and review far more closely.

Keep voice off the table

Worth saying clearly, because it’s where these passes go wrong: a style guide is about consistency of format and mechanics, not flattening your voice. The risk with AI is that, given latitude, it sands every post into the same neutral tone. Constrain it to your explicit rules, and review the diff for any place it reached past them. Your readers come for how you write; the goal is to fix the typos-of-consistency without touching the personality.

Review the diff, then publish

A style pass touches a lot of lines, so reviewing matters — and it’s free. Read the diff to confirm the edits stayed within your rules, then Specter shows which posts would update before anything goes live. Every publish keeps a snapshot behind it, so a rule you’d word differently is one revert away. If you haven’t connected Specter yet, the first-sync guide gets you there; browsing and reviewing cost nothing, only the AI run spends credits, and your workspace opens with 500 free.

This is the most “operations” of the AI jobs, and it sits alongside the others — bulk SEO edits, tag cleanup, fixing outdated facts — that become routine once your whole blog is a workspace you can run a recipe over. Consistency stops being aspirational and becomes something you can simply enforce. Subscribe now →

---

Prefer to run the style pass on your own machine, over .md files with your own AI? The desktop and open-source edition does it locally.