Anti AI Writing

Anti-AI Writing

The goal is not "don't sound like AI." That framing loses — blocklists rot, and chasing a negative gives you a beige voice. The goal is: sound like a specific person who has thought about the thing and has something to say. Specificity is the moat. Voice is the moat. Everything below serves those two.

Apply with judgment. Spirit beats letter. If a rule makes the sentence worse, break it.

Where this runs

This skill matters most on written content — text a reader's eye scans. Run the full pass there: captions, carousels, newsletters, threads, LinkedIn, long-form, DMs, landing copy. It's the last filter on every written piece.

On spoken content (reel and video scripts — the words get said aloud), run the spoken subset only:

• Apply: specificity (Level 3+), kill hollow reframes that don't pay off, cut borrowed-authority / thinkfluencer filler, cut significance inflation. These hurt out loud too.
• Skip: the formatting tells (em dashes, bullets, hashtags don't exist in speech), and go light on the vocab blocklist — spoken cadence forgives, and your voice plus the viral-hooks and storytelling skills are already doing the heavy de-AI-ing. Over-applying prose rules to a script makes it sound stilted, not human.

The split can live inside a single piece. When you produce a reel, the script is spoken (subset), but the caption that ships with it is written (full pass). Apply the right intensity to each part of the output, not one blanket pass.

The 5 diseases (diagnose before you fix)

Most AI writing fails for one of five reasons. Name the disease and the fix is obvious. If you can't name it, read the line aloud — the disease becomes audible.

1. Vagueness compression — describes a category, not a thing. "Users were frustrated" → "users clicked export six times because nothing loaded."
2. Significance inflation — treats normal facts like turning points. "This marks a pivotal shift in onboarding" → state the fact, let the reader weigh it.
3. Hedged confidence — has a position but won't commit. "It could be argued that…" → take the position or cut the sentence.
4. Rhythmic flatness — every sentence the same length, every paragraph three sentences. → break the meter.
5. Borrowed authority — sounds like a McKinsey deck or a LinkedIn thinkfluencer. No fingerprint. → write it the way you'd say it to one person.

Rule priority (when rules collide)

Accurate > Clear > Specific > Voiced > Stylish. Never sacrifice accuracy for style. A boring true sentence beats an elegant vague one.

Specificity — the whole game

The single highest-leverage rule. Specific beats polished, every time. The ladder:

Aim for level 3 minimum, level 4 if you have it. Replace categories with instances, adjectives with numbers, "users" with "the kind of user who [does specific thing]." If you don't have the specific, get it before writing — or admit it plainly ("I don't know the exact number, but it felt like roughly half"). Pull real specifics from your own notes and lived experience; never invent numbers or events.

The negative parallelism ban (the #1 tell)

The biggest single tell of AI writing. The pattern:

"It's not X. It's Y."

…and every variation that knocks down a frame to sound insightful: Not X. Y. / Less X, more Y. / Stop thinking X, start thinking Y. / The real question isn't X, it's Y. / It was never about X, it was always about Y. Plus the softer forms: Most people think X, but… / On the surface X, but really Y. / X gets all the attention, but…

The pivot words that signal it when they follow a rejected frame: but, actually, really, instead, rather, ultimately, the truth is, what matters is, the real, the hidden, the overlooked. These words are everywhere in good prose — only count one as a hit when it follows a rejected frame, never on sight. The reframe also crosses sentence boundaries ("Most teams think they have a hiring problem. They have a standards problem.") and hides in rhetorical questions ("Is this a productivity problem? No. It's an attention problem.") — but the boundary-crossing form is banned only when B is hollow; a concrete B across a boundary is fine (see the reconciliation test below).

The fix: delete the rejected half, then rewrite the positive half as a direct claim with specifics.

"It's not about the prompt. It's about the context." → "It's about the context." → "The model performs 3× better when you paste the prior chat into the system prompt."

The reframe was hiding the fact that the writer didn't have a point. The final version has a number and a mechanism — the actual point.

Reconciliation with viral-hooks (important — these skills must not fight): hooks deliberately use A-vs-B contrast as a curiosity mechanic, and that's allowed. The line is hollow vs earned:

• Banned (hollow): B is vague significance that hides the absence of a point — "it's not about tactics, it's about mindset." Cut it.
• Allowed (earned): B is concrete and the content delivers it — "Most people meal prep Sunday. The most consistent clients I know prep nothing and cook one thing daily." The contrast opens a loop the piece actually pays off.
• Test (two parts): (1) Is B concrete — Level 3+ on the specificity ladder above (an instance, number, or mechanism, not a category like "mindset" or "systems")? (2) Does the body deliver it? At hook stage the body doesn't exist yet — so judge B on part (1) alone, keep it provisionally, and re-check delivery on the post-draft pass. A vague-significance B fails part (1) and gets cut immediately. In spoken hooks the bar is looser (contrast is a format convention); in written prose, hold the line hard.

Analogy & metaphor control

Default: write literally. Most business/tech analogies make weak thinking sound vivid — they help the writer feel clever, not the reader understand.

Use an analogy only if all five are true: (1) the subject is genuinely unfamiliar/abstract, (2) it makes understanding easier not just prettier, (3) it's shorter than the literal explanation, (4) it's exact enough not to mislead, (5) it sounds normal aloud. Any test fails → write literally. Frequency: under 800 words, zero by default; ~one per 1,500 words after.

Banned metaphor families for abstract work: journeys, battlefields, machines-for-people, ecosystems, engine/fuel, North star, flywheel, DNA, scaffolding, plumbing, iceberg, bridge, chess, sports. Banned metaphor verbs: baked in, bolted on, woven, layered, distilled, unpacked, crystallized, surfaced, amplified, threaded, sculpted, anchored, framed. Replace with literal verbs: cut, added, removed, caused, showed, reduced, fixed, named, chose.

"Your onboarding is a leaky bucket." → "Users leave during onboarding." → "42% drop on step 2 because the form asks for billing before showing the product."