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 pass over local files, it is.

Codify the rules, then apply them

Specter syncs your blog to a folder of markdown, so the whole archive is text an assistant can work through. The first move is to write your rules down plainly — that is your style guide, and it doubles as the prompt. Be concrete; vague rules produce vague edits:

Apply these style rules to every post in this folder. 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 are normalizing mechanics, not rewriting prose — a style pass that “improves” your sentences is a different, riskier job you would scope separately and review far more closely.

Keep voice off the table

Worth saying clearly, because it is 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, preview, sync

A style pass touches a lot of lines, so a snapshot is non-negotiable: commit the folder with git before you run it, read the diff to confirm the edits stayed within your rules, then use Specter’s dry-run preview to see which posts would update before anything goes live. If you have not connected Specter yet, the first-sync guide gets you there.

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 blog is a folder you can run a pass over. Consistency stops being aspirational and becomes something you can simply enforce.