Skip to content

The kill list

AI writing has a vocabulary. Once you can see it, you cannot unsee it, and neither can your reader.

9 min read

Level 0

Curious

0 XP
150 XP to ApprenticeNo streak yet0 badges0% done

There is a specific set of words and shapes that AI writing reaches for. Not because they are wrong, but because they are the safest possible choice at every turn.

Safe at every turn, for two thousand words, is exactly what sounds like a machine.

The words

Delete these on sight. No exceptions, no "but sometimes it fits".

delve        crucial      pivotal      vibrant
vital        foster       showcase     underscore
landscape    tapestry     testament    intricate
interplay    enduring     profound     garner
enhance      boasts       renowned     nestled
seamless     robust       powerful     groundbreaking
skyrocket    supercharge  game-changing
Read that list out loud. You have seen every one of them this week.

The phrases

  • "In today's fast-paced world" and every variant of it
  • "plays a crucial role in"
  • "it's important to note that"
  • "when it comes to"
  • "at the end of the day" and "the bottom line"
  • "in conclusion" and "in summary"
  • "this is a testament to"

The shapes, which matter more than the words

Anyone can find-and-replace a word list. The structures are what actually give it away, and they need a human to spot.

Staccato

  • "No API costs."
  • "Your code never leaves your machine."
  • "Works offline."
  • Four short declaratives in a row reads like a feature list wearing a costume.

Woven

  • "Running locally means your code stays on your machine, so you're not paying API costs, and it works offline."
  • One sentence. Same three facts. Sounds like a person.

Contrastive negation is the sneakiest one

"It's not X, it's Y." "It's not just about X, it's about Y." Fine once, for a genuine distinction. Used three times in an article it becomes a profundity crutch, and it is the single most reliable tell in AI prose.

The four rules that fix most of it

  1. 1.Concrete over abstract. Every abstract claim gets a number, a name, or an example within a sentence or two. "Affordable" becomes "$39 a month".
  2. 2.Name your sources. "Nielsen Norman found," never "studies show." If you cannot name it, cut the claim.
  3. 3.Short sentences. Aim for 15 to 20 words. One short one for emphasis.
  4. 4.Read it aloud. If you would not say it to a friend, rewrite it.
Challenge

Spot the slop

130 XP+33 perfect

One paragraph. Ten planted problems. Tap every word or phrase that has to go. Careful: cutting something clean costs you a point, because over-editing is its own defect. A perfect run unlocks the Slop slayer badge.

11 problems planted0 flagged

Do this now

  1. 1

    Download the kill list from this module's reward and save it in your project.

    mkdir -p references
    # save the file as references/styling.md
  2. 2

    Point your CLAUDE.md at it in one line.

    No AI slop. Follow references/styling.md, every article, every client.
  3. 3

    Run it over something you published before you had it.

    > Check this article against references/styling.md.
    > List every violation with the line. Do not rewrite anything yet.

    Ask for the list first. If you ask for a rewrite you will get a rewrite, and you will not learn which patterns are yours.

Finished reading?

Mark it done to bank the XP and keep your streak alive. Any challenges on this page score separately, so you can come back for a perfect run later.