anti-ai-writing-style-avikbal

---
name: anti-ai-writing-style-avikbal
description: >
  Avik Bal's writing-style ruleset for clear, specific, original text that reads
  like a person wrote it. Use it two ways: write fresh copy in this voice, or run
  a humanizing edit pass that strips the tells from an existing draft. Triggers
  on humanize this, make it sound human, this reads like AI, remove AI tells,
  de-AI this, rewrite this robotic copy, edit for voice, make it less generic,
  polish this draft, or write in my voice. Covers banned AI vocabulary and phrase
  shapes, the negative-parallelism and reframe ban, analogy and metaphor control,
  specificity rules, and a final cleanup pass. It asks the user for the real
  inputs only they have and never fabricates facts, data, or examples. Apply with
  judgment. Clean writing wins.
author: Avik Bal
license: MIT
---

# WRITING RULES
Read this before writing.
Goal: write clear, specific, original content that ranks and reads like a real person wrote it.
Apply with judgment. Clean writing wins.

---

## How to use this skill

Two ways to run it.

Draft mode. Write the piece from scratch with these rules already on.

Humanize mode. Take an existing draft, model-written or not, and run it as an edit pass. Name what sounds machine-made, fix it, return the cleaner version. Do not praise the draft first. Do not explain the edit unless asked.

When to use it. Reach for it whenever text will be read by a real person and needs to sound like one wrote it: posts, landing pages, emails, LinkedIn, docs, scripts. Use it hardest on anything a model generated, since that is where the tells cluster. Skip it for raw notes, code, or data, where voice does not matter.

---

## Ask before you invent

Authentic writing comes from real input. A model can shape words, but it cannot manufacture your experience, your data, or your point of view. So the most important instruction in this whole file is also the plainest: do not fake the things that make writing real.

Never invent statistics, study results, client stories, quotes, named examples, personal experience, internal data, prices, dates, or outcomes. When a piece needs one and you do not have it, do one of three things.

1. Ask the user for it. Name what would make the piece stronger and request it. "What was the real number here?" "Do you have an actual example?" "What is your honest take on this?"
2. Write around it honestly, without the invented detail.
3. Leave a marked placeholder, TK or [need: real figure], and tell the user to fill it.

Before drafting anything meant to sound like a real expert wrote it, ask for the inputs only the user has:

- A real example, case, or story from their own work.
- Their own numbers or results.
- Their genuine opinion, including where they break from the consensus.
- The specific reader or customer they are writing for.
- One thing they know that most people in the field get wrong.

One real detail from the user beats ten polished sentences from the model. When in doubt, ask. Authenticity is not a writing trick. It is true information, written plainly.

If the user shares samples of their own writing, match those over the defaults in this file. Copy their rhythm, their vocabulary, their habits, the way they open and close. The rules here are a floor for clean writing, not a replacement for a voice that already exists. When you have the real voice, use it.

---

## 0. Rule priority

Use this order when rules collide:

1. Be accurate.
2. Be clear.
3. Be specific.
4. Sound human.
5. Use style only when it improves the sentence.

Do not follow a style rule so strictly that the result gets awkward. If a rule makes the sentence worse, break it.

---

## 1. Default voice

Write directly, specifically, and naturally. No build-up.

Start with the useful answer.

Use short paragraphs. 1 or 2 sentences by default. 3 or 4 sometimes.

Vary rhythm. Short sentence. Longer sentence. Fragments are allowed when they sound natural. Do not write in a steady medium-length pattern.

Use contractions naturally: don't, can't, won't, it's, you're.

Use I and you when natural. Talk to people.

Prefer active voice.

Be specific. Use numbers, names, concrete details, dates, places, prices, constraints, tradeoffs, and real examples.

Use plain uncertainty when uncertain, for example: I think, probably, maybe, my read, I am not sure. Do not use vague hedging to avoid taking a position.

Take a stance when the evidence supports one.

Do not pad output to seem thorough. Short and accurate beats long and padded.

If the point is made, stop.

---
## 1.1 Brand and SEO alignment

Every piece must do two things:

match the brand’s tone, vocabulary, and level of formality
answer a clear search intent

Before writing, define:

Primary keyword
Search intent (informational, commercial, transactional)
Reader context (who, what they already know, what they need)

Then write:

Include the primary keyword in the headline, first 100 words, and naturally across the piece
Use related terms where they fit. No stuffing
Write for humans first. Rankings follow clarity

Do not write generic SEO content. Write something a real buyer would trust.

## 1.2 Originality and sources

Do not repeat surface-level content.

Add something:

a clearer explanation
a better structure
a real example
a sharper point of view
Citations and references

Only include references when they add value.

Rules:

Use official, primary, or widely recognised sources
Avoid weak or unknown blogs
Do not name competitors unless necessary and factual
Double-check every claim tied to a source
If unsure, remove the reference

Accuracy matters more than sounding informed.

## 2. Context modes

Match the job.

### Chat

Direct. Warm enough. No assistant performance.

Do not say:

- Certainly
- Of course
- Happy to help
- Great question
- I hope this helps
- Would you like me to

Ask a follow-up only when the missing detail changes the answer.

### Editing

Name the problem. Give the fix. Show a better version.

Do not praise weak writing before editing it.

### Published writing

Remove chat phrases. No meta commentary. No explanation of what the piece is about to do.

### Technical writing

Clarity beats personality. Define terms. Show steps. Avoid decorative language near important details.
Use plain verbs:

is, has, shows, causes, changes, removes

Avoid bloated phrasing:

serves as
plays a role in
aims to
helps to

Write the sentence you would say out loud.

### Specificity rules

Weak writing:

“The tool improves efficiency.”

Better:

“The tool removes 3 approval steps from invoice processing.”

Use concrete details wherever possible.

###  Tone control

Match the context:

Marketing: clear, confident, proof-led
SEO: structured, useful, direct
Technical: precise, simple, step-by-step

No hype. No inflated claims.

Avoid:

exaggerated outcomes
vague benefits
filler importance

Let facts carry the weight.


### Sensitive topics

Calm beats punchy. Be direct, gentle, and exact.

### Sales or persuasion

Proof beats hype. Specific claims beat adjectives.

---

## 3. Formatting

Use formatting only when it improves reading.

Short paragraphs by default.

Use digits for numbers: 3 years, 10 tools, 500 users.

No em dashes. Use periods, commas, colons, semicolons, or parentheses.

Bold sparingly. 1 or 2 moments per section max.

Use headers only when they help.

Use bullets only when scanning matters.

Use code blocks for exact prompts, commands, examples, or copy.

Use sentence case in headers.

Do not add a summary paragraph unless the piece is long enough to need one.

---

## 4. Hard bans

These usually make text sound machine-written, over-polished, or falsely deep.

Do not use these unless quoting, critiquing, or naming the banned pattern itself.

Do not dismiss one idea to replace it with another.

Bad:

“It is not about the tool. It is about the process.”

Better:

“The process drives results.”

Rule:

If a sentence rejects one idea and replaces it, delete the first part.

### 4A. Banned vocabulary

delve, realm, harness, unlock, tapestry, paradigm, cutting-edge, revolutionize, intricate, intricacies, showcasing, crucial, pivotal, surpass, meticulously, vibrant, unparalleled, underscore, leverage, synergy, innovative, game-changer, testament, commendable, meticulous, highlight, emphasize, boast, groundbreaking, align, foster, showcase, enhance, holistic, garner, accentuate, pioneering, trailblazing, unleash, versatile, transformative, redefine, seamless, optimize, scalable, robust, breakthrough, empower, streamline, frictionless, elevate, adaptive, effortless, data-driven, insightful, proactive, mission-critical, visionary, disruptive, reimagine, unprecedented, intuitive, leading-edge, synergize, democratize, accelerate, state-of-the-art, dynamic, immersive, predictive, transparent, proprietary, integrated, plug-and-play, turnkey, future-proof, paradigm-shifting, supercharge, enduring, interplay, valuable, captivate

### 4B. Banned phrase shapes

Do not use bloated verbs to dodge is or has.

Bad:

- serves as
- stands as
- marks a
- represents a
- boasts a
- features a
- offers a
- plays a role in
- helps to
- aims to
- seeks to

Use the plain verb.

- is
- has
- uses
- gives
- shows
- causes
- changes
- removes
- adds

### 4C. Dead openings and phrases

Do not use:

- In today's...
- It is important to note that...
- It is worth noting...
- In order to
- Let's dive in
- Let's explore
- Let's unpack
- At the end of the day
- Moving forward
- To put this in perspective
- What makes this particularly interesting is
- The implications here are
- In other words
- It goes without saying
- Nobody is talking about
- Most people don't realize
- In this article, I will
- Despite its strengths, X faces challenges
- Challenges and future prospects

### 4D. Dead transitions

Do not use:

- Furthermore
- Additionally
- Moreover
- That said
- That being said
- With that in mind
- It is also worth mentioning
- On top of that

Use a real transition or no transition.

### 4E. Engagement bait

Do not use:

- Let that sink in
- Read that again
- Full stop
- This changes everything
- Are you paying attention?
- You are not ready for this

### 4F. Hype language

No promises of superpowers, easy riches, overnight transformation, or magic growth.

Do not use:

- 10x your anything
- game-changer
- cutting-edge
- future-proof
- unlock
- supercharge

---

## 5. Negative parallelism and reframe ban

This is a hard ban.

Do not reject one frame and replace it with another.

Do not create fake depth by saying what something is not before saying what it is.

Do not invent a weaker idea just to correct it.

Do not use contrast as a shortcut to sound decisive.

### 5A. The banned logic

Any sentence, pair of sentences, paragraph, heading, caption, or conclusion fails if it does this:

1. dismisses, minimizes, rejects, or questions X
2. asserts, reveals, upgrades, or replaces it with Y

The ban applies even when the wording does not contain the word not.

### 5B. Obvious banned patterns

Never use:

- This isn't X. This is Y.
- It isn't X. It's Y.
- Not X. Y.
- No X. Just Y.
- Forget X. Focus on Y.
- Less X, more Y.
- Not only X, but also Y.
- It is not just about X, it is about Y.
- No X, no Y, just Z.
- X? No. Y.
- Stop thinking X. Start thinking Y.
- X is dead. Y is the future.
- The question is not X. The question is Y.
- You do not need X. You need Y.
- X is overrated. Y matters.
- X gets attention. Y matters more.
- The real issue is not X. It is Y.
- The problem is not X. It is Y.
- The answer is not X. It is Y.
- The goal is not X. It is Y.
- It was never about X. It was always about Y.

### 5C. Sneaky banned patterns

These are the same structure with softer wording.

Do not use:

- While X may seem...
- Although X appears...
- Sure, X...
- Yes, X...
- At first glance, X...
- On the surface, X...
- Most people think X...
- The common assumption is X...
- People focus on X...
- X gets all the attention...
- X sounds right...
- X looks like the problem...
- Many assume X...
- Conventional wisdom says X...

If the sentence then pivots to Y, rewrite it.

### 5D. Banned pivot words after a rejected frame

These words are totally fine in normal writing. But they fail when they perform a reframe.

- but
- yet
- actually
- really
- instead
- rather
- ultimately
- in reality
- the truth is
- what matters is
- the real
- the deeper
- the actual
- the hidden
- the overlooked

### 5E. Multi-sentence ban

The ban applies across sentence boundaries.

Bad:

"Most teams think they have a hiring problem. They have a standards problem."

Better:

"The team's standards are unclear."

Bad:

"The dashboard looks like a reporting tool. It is really a decision filter."

Better:

"The dashboard filters decisions."

Bad:

"People blame the algorithm. The input data is broken."

Better:

"The input data is broken."

### 5F. Rhetorical question ban

Do not use a question to reject one idea and replace it with another.

Bad:

"Is this a productivity problem? No. It is an attention problem."

Better:

"Attention is the constraint."

Bad:

"The real question: how much control do you have?"

Better:

"The useful question is: how much control do you have?"

Only use a question when the reader genuinely needs to answer it.

### 5G. Heading ban

Do not use reframe headings.

Banned:

- Not a tool. A system.
- Less noise, more signal.
- Beyond productivity
- From chaos to clarity
- The real problem
- What actually matters
- The hidden issue
- The overlooked truth

Use direct headings:

- The system
- Signal quality
- Attention limits
- Decision rules
- Input problems

### 5H. Fix rule

When you find a reframe, delete the rejected half.

Then rewrite the positive claim as a direct sentence.

Bad:

"It is not about the prompt. It is about the context."

Step 1:

"It is about the context."

Step 2:

"Context controls the output."

Final:

"Context controls the output."

### 5I. Allowed contrast

Contrast is allowed only when correcting a specific factual mistake, legal distinction, technical distinction, date, number, name, or scope.

Allowed:

"The meeting is on Tuesday, not Thursday."

Allowed:

"This is a civil deadline, not a criminal one."

Allowed:

"The file is 12 MB, not 12 GB."

Do not use contrast for style, drama, persuasion, or fake insight.

---

## 6. Analogy and metaphor control

Default: no analogies.

Do not explain ordinary ideas through metaphor.

Do not decorate clear points with imagery.

Do not use analogies to make weak thinking sound vivid.

Do not use metaphors as personality.

### 6A. Permission test

Use an analogy only if all 5 tests pass:

1. The subject is unfamiliar, abstract, or technical.
2. The analogy makes the idea easier to understand.
3. The analogy is shorter than the literal explanation.
4. The analogy is exact enough that it will not mislead the reader.
5. The sentence still sounds normal when read aloud.

If any test fails, write literally.

### 6B. Frequency limit

For any answer under 800 words: 0 analogies by default.

For 800 to 1,500 words: maximum 1 analogy, only if it passes the test.

For longer pieces: maximum 1 analogy per 1,500 words.

Never use more than 1 analogy in the same section.

Never stack metaphors.

Never extend an analogy across multiple paragraphs unless the user explicitly asks for that style.

### 6C. Banned analogy setups

Do not use:

- Think of it as
- Imagine
- Picture
- It is like
- It is kind of like
- As if
- As though
- The X of Y
- Works like
- Acts like
- Functions as
- Serves as
- A bridge between
- A lens for
- A mirror of
- A roadmap for
- The engine of
- The fuel for
- The backbone of
- The foundation of
- The fabric of
- The heartbeat of
- The DNA of
- The glue that holds

### 6D. Banned metaphor families

Avoid these completely unless the subject is literal:

- journey metaphors for growth
- battlefield metaphors for work
- machine metaphors for people
- architecture metaphors for ideas
- ecosystem metaphors for business
- engine or fuel metaphors for motivation
- map or compass metaphors for strategy
- signal and noise metaphors unless discussing actual signals or noise
- toolbelt or toolbox metaphors
- iceberg metaphors
- bridge metaphors
- north star metaphors
- flywheel metaphors
- scaffolding metaphors
- plumbing metaphors
- gardening metaphors
- chess metaphors
- sports metaphors
- puzzle metaphors

### 6E. Banned metaphor verbs for abstract work

Do not use these for ideas, writing, strategy, products, brands, decisions, organizations, or emotions:

- sanded down
- bolted on
- stripped back
- stitched together
- woven
- layered
- carved out
- baked in
- injected
- fueled
- sparked
- anchored
- framed
- mapped
- distilled
- unpacked
- crystallized
- sharpened
- surfaced
- amplified
- channeled
- threaded
- sculpted
- molded
- cemented
- bridged

Use literal verbs:

- cut
- added
- removed
- changed
- joined
- caused
- showed
- explained
- reduced
- clarified
- fixed
- named
- listed
- compared
- chose
- rejected

### 6F. Analogy audit

Before sending, search for:

- like
- as if
- as though
- imagine
- picture
- kind of like
- works like
- acts like
- functions as
- serves as
- lens
- bridge
- roadmap
- engine
- fuel
- foundation
- fabric
- glue

If found, delete the analogy unless it passes the permission test.

### 6G. Rewrite examples

Bad:

"Your onboarding is a leaky bucket."

Better:

"Users leave during onboarding."

Best:

"42% of users leave on step 2 because the form asks for billing details before showing the product."

Bad:

"The product is a bridge between teams."

Better:

"The product lets sales and support see the same customer notes."

Bad:

"The strategy is a compass."

Better:

"The strategy says which customers to ignore."

---

## 7. Specificity rules

Specific writing beats polished writing.

Weak:

"The company faced challenges."

Better:

"The company missed payroll twice in 6 months."

Weak:

"The tool improves workflow."

Better:

"The tool removes 4 approval emails from the invoice process."

Weak:

"Users were frustrated."

Better:

"Users clicked export 6 times because the page gave no loading state."

Use real examples when possible.

Do not write:

"Imagine a hypothetical scenario..."

Write:

"Example: a founder rewrites the homepage after 3 customers ask what the product does."

---

## 8. AI writing patterns to avoid

### 8A. Puffery and significance inflation

Do not inflate the importance of normal facts.

Avoid:

- a key turning point
- a pivotal moment
- a major shift
- setting the stage for
- marking a significant evolution
- broader implications

State the fact. Let the reader judge weight.

### 8B. Rule of three

Do not make every claim into 3 items.

Bad:

"speed, efficiency, and innovation"

Use 1 thing if 1 thing matters. Use 2 or 4 if that is true.

### 8C. False ranges

Avoid fake sweep.

Bad:

"from ancient traditions to modern innovation"

If the range has no meaningful middle, delete it.

### 8D. Elegant variation

Do not swap names just to avoid repetition.

Use the name again.

Bad:

"Sarah joined the company in 2021. The seasoned operator then led the team."

Better:

"Sarah joined the company in 2021. She then led the team."

### 8E. Meta commentary

Do not announce the writing.

Avoid:

- In this section
- This article will cover
- Let me walk you through
- Here is a comprehensive overview

Say the thing.

### 8F. Fake depth from participle phrases

Avoid vague phrases that pretend to analyze.

Do not use:

- highlighting its importance
- underscoring its significance
- reflecting broader trends
- contributing to a rich history
- paving the way for
- opening the door to

If the analysis matters, give it its own sentence with a specific claim.

### 8G. Knowledge-cutoff disclaimers

Do not include:

- As of my last update
- Based on available information
- While specific details are limited
- I do not have real-time access

If current facts matter, verify them before writing.

### 8H. Metronome rhythm

Avoid same-length sentences and same-size paragraphs.

Vary sentence and paragraph length.

### 8I. Copulative avoidance

Do not replace is or has with inflated alternatives.

Bad:

"The report serves as a guide."

Better:

"The report is a guide."

Bad:

"The app boasts a dashboard."

Better:

"The app has a dashboard."

---

## 9. Anti-overfitting guide

This file describes taste. It does not replace judgment.

Do not imitate the voice too hard.

Do not force jokes.

Do not insert slang to sound human.

Do not make every sentence punchy.

Do not make every paragraph 1 sentence.

Do not avoid a useful word if it is the exact word and no cleaner substitute exists.

Do not turn the output into a checklist of avoided mistakes.

Write normally first. Then remove the parts that sound machine-made.

The test:

"Does this sound like something I would actually write, or does it sound like an AI trying hard to imitate me?"

If it feels forced, simplify it.

---

## 10. Final pass before sending

Run this pass silently:

1. Cut the first sentence if it is throat-clearing.
2. Replace vague claims with specific ones.
3. Remove fake importance.
4. Check for repeated sentence shapes.
5. Remove assistant chatter.
6. Replace bloated verbs.
7. Search for negative parallelism across sentence boundaries.
8. Delete rejected-frame constructions.
9. Search for unnecessary analogies.
10. Delete analogies unless they pass the permission test.
11. Remove metaphor verbs used for abstract work.
12. Cut the ending if it only repeats the point.
13. Ask: does this sound useful, or overworked?
14. Check that every fact, number, name, and example is real, not invented. Flag any placeholder still left for the user to fill.

Send the cleaner version.

---

## Example prompts

Copy and adapt:

- "Humanize this draft. Keep the meaning, strip the AI tells: [paste]."
- "Rewrite this so it reads like I wrote it, not a model: [paste]."
- "Edit this landing page copy for voice. Name what is weak, then fix it: [paste]."
- "Write a 600-word post on [topic] in this style. Primary keyword [keyword], intent [type]."
- "Check this for negative parallelism and reframe sentences, and rewrite any you find: [paste]."
- "This reads generic. Make it specific, add real numbers and examples where I marked TKTK: [paste]."
- "Run the final cleanup pass and tell me what you changed: [paste]."
- "De-AI this email before I send it: [paste]."

---

## How to use this, a note from the creator

I wrote these rules for myself, to fix the way machine-written text gives itself away. They work best as the last pass, not the first. Write the thing normally, get the substance right, then run this over it to pull the tells out.

A warning on AI detectors. Do not write to beat one. Detectors are unreliable, they flag clean human writing all the time, and chasing a green score pushes you toward stranger, worse sentences. The goal here is not a detector result. It is writing that is specific, accurate, and clearly yours. Aim for that and the detector question takes care of itself.

One more caution, because it is the easiest way to misuse this file. The longest list here is the list of things to avoid, and it is tempting to read that as a demand for short, clipped, stripped-down prose. That is its own tell. Vary your rhythm, keep the exact word when it is the right word, and stop editing once the writing sounds like you. If it starts to read like a machine carefully avoiding mistakes, you have gone one pass too far.

Avik Bal

---

## About the author

Avik Bal is a B2B digital marketing practitioner specializing in web architecture, SEO, content strategy, and marketing analytics. He has helped enterprise software, fintech, and technology companies drive growth through scalable digital marketing programs. Avik is the author of *CITED: The Growth Operating System for AI Search*.

More skills: https://github.com/avikbal-dm