> **How to use this file**: it is a catalog of smells, not a checklist to run top to bottom. The principles in `SKILL.md` Core Stance apply here too: over-editing is failure, the author's voice and genre win, and these lists are examples, not find-and-replace. A sentence that already reads natural stays. Match the smell, not the word. One trope used once may be fine; several together, or one repeating, is the smell.
## English Scenario
Eliminate predictable AI writing patterns. Write like a human: varied, imperfect, specific.
### Core Rules
1. **Cut filler phrases.** Remove throat-clearing openers ("It's worth noting", "Notably,", "Importantly,"), emphasis crutches, and adverbs that only signal emphasis. Keep adverbs that carry real meaning.
2. **Break formulaic structures.** Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency.
3. **Use concrete subjects.** People, software and physical objects can all do things. Remove agency that obscures who acted or how something works; do not force a human subject into every technical sentence.
4. **No vague declaratives.** "The reasons are structural", "The reality is simpler", "History is clear": name the specific thing and show the evidence before the conclusion. No lazy extremes ("every," "always," "never") doing vague work.
5. **Preserve viewpoint.** An author's experience stays "I"; translating it as "you" can turn a personal account into unsolicited advice.
6. **Keep natural rhythm.** Repair fragment-heavy or repetitive prose without quotas for sentence length, list size or paragraph endings.
7. **Trust readers.** Cut hand-holding, but keep uncertainty, attribution and conditions that limit a claim.
8. **Preserve emotional meaning.** A personal conviction or heartfelt ending can sound quotable and still belong. Keep its warmth and force; cut added stock morals, not the author's feelings. Translation must carry the emotion as well as the facts.
9. **Do not replace one formula with another.** “Human” does not mean slangy, quirky, or performatively casual.
10. **No emoji.** Remove any emoji from the text being edited.
### Word Choice
Examples, not exhaustive -- any word used to signal importance rather than to say something is suspect.
**Overused emphasis adverbs (cut these when they only signal importance, not every adverb):**
"quietly", "deeply", "fundamentally", "remarkably", "arguably", "certainly", "really", "just", "literally", "genuinely", "honestly", "simply", "actually"
> NO: "quietly orchestrating workflows"
> OK: Say what it does. Drop the adverb.
**AI vocabulary: replace with plain language:**
| Avoid | Use instead |
|-------|-------------|
| delve (into) | examine, look at, explore |
| leverage (as verb) | use |
| utilize | use |
| robust | strong, reliable, solid |
| streamline | simplify, cut |
| harness | use, apply |
| navigate (challenges) | handle, address |
| unpack | explain, examine |
| paradigm | system, approach, model |
| synergy | combination, cooperation |
| ecosystem | community, network, field |
| tapestry | mix, combination |
| landscape | situation, field, area |
| game-changer | significant, important |
| deep dive | analysis, examination |
| moving forward | next, from now |
**Pompous copulas: use "is" instead:**
> NO: "serves as", "stands as", "marks", "represents"
> OK: "is"
### Sentence Structures to Avoid
Examples, not exhaustive -- any construction that performs insight rather than delivers it belongs here.
**Negative parallelism**: the single most common AI tell:
> NO: "It's not bold. It's backwards." / "Not because X, but because Y." / "The question isn't X. The question is Y." / "Not a bug. Not a feature. A fundamental design flaw."
> OK: State Y directly. Drop the negation entirely.
**Rhetorical self-questions:**
> NO: "The result? Devastating." / "The worst part? Nobody saw it coming."
> OK: State it: "The result was devastating."
**Anaphora abuse**: repeating the same sentence opener:
> NO: "They assume that... They assume that... They assume that..."
> OK: Combine or restructure. One statement, clear subject.
**Tricolon abuse**: rule of three, used three times back to back:
> NO: "Products impress people; platforms empower them. Products solve problems; platforms create worlds." / "Apple didn't build Uber. Facebook didn't build Spotify. Stripe didn't build Shopify."
> OK: Make the point once, cleanly. One example is enough.
**False ranges:**
> NO: "From innovation to cultural transformation" (what's in between?)
> OK: List the two things directly, or pick one.
**Dramatic fragmentation**: manufactured emphasis via fragments, inside a sentence or as whole paragraphs:
> NO: "He published this. Openly. In a book. As a priest." / "These weren't just products. And the software side matched. Then it professionalised."
> OK: Complete sentences. Trust content over presentation.
**False agency**: a metaphor substitutes for the actual mechanism:
> NO: "The data wants a cleaner narrative."
> OK: Name what the data supports or who made the decision. "The tool reads the file" is ordinary technical English and stays.
### Tone Patterns to Avoid
**False suspense transitions:**
> NO: "Here's the kicker." / "Here's the thing." / "Here's where it gets interesting."
> OK: Make the point. No buildup.
**Patronizing analogies:**
> NO: "Think of it like a highway system for data." / "Think of it as a Swiss Army knife."
> OK: Explain the concept directly. If an analogy helps, test it against three criteria before keeping it: (1) remove it and the paragraph collapses: it is load-bearing, not decorative; (2) push it one layer deeper and it still holds; (3) the reader gets it without further explanation. If it fails any of these, drop the analogy and state the idea directly.
**Futurist invitation:**
> NO: "Imagine a world where every tool you use has a quiet intelligence behind it..."
> OK: Describe what actually exists or what you're actually proposing.
**False vulnerability**: performative self-awareness:
> NO: "And yes, I'm openly in love with the platform model"
> OK: Real vulnerability is specific and uncomfortable. Skip the polish.
**Grandiose stakes inflation:**
> NO: "This will fundamentally reshape how we think about everything." / "will define the next era of computing"
> OK: Say what it actually does.
**Pedagogical hand-holding**, including the sentence that announces a list or classification:
> NO: "Let's break this down step by step." / "Let's unpack what this really means." / "Community data is an interesting piece. Diversity has to cover..." / "One detail is easy to miss. 'Output action' can mean..."
> OK: Start with the content: "Community data needs to cover different lighting, camera angles and rooms."
**Vague attributions:**
> NO: "Experts argue..." / "Industry reports suggest..." / "Observers have cited..."
> OK: Name the expert, link the report, quote the person. If you can't, you don't have a source.
**Invented concept labels**: compound labels that sound analytical but aren't grounded:
> NO: "the supervision paradox" / "the acceleration trap" / "workload creep"
> OK: Describe the thing directly. Don't name it as if it's an established term.
### Paragraph & Composition Patterns to Avoid
**Bold-first bullets**: every bullet starts with a bolded phrase:
> NO: "**Security**: Environment-based configuration..." / "**Performance**: Lazy loading..."
> OK: Write bullets as sentences, or drop the bold. Not every list needs labels.
**Fractal summaries**: "what I'm going to tell you; what I'm telling you; what I just told you":
> NO: "In this section, we'll explore... [3000 words later] ...as we've seen in this section." / "In conclusion..." / "To sum up..."
> OK: Skip the preview and the recap. Write the content, then end without announcing the ending.
> Exception: a single closing sentence in a TL;DR that orients non-specialist readers to the structure ahead ("The rest of this piece follows X in order...") is intentional navigation, not a fractal summary. Keep it; flag it at most, but do not delete without author approval.
**The dead metaphor**: one metaphor used 10 times across a piece:
> NO: "The ecosystem needs ecosystems to build ecosystem value."
> OK: Use a metaphor once, then move on.
**One-point dilution**: same argument restated 10 ways across 4000 words:
> OK: Say it once. Add evidence or move on.
**"Despite its challenges..." formula:**
> NO: "Despite these challenges, the initiative continues to thrive."
> OK: Either address the challenges or don't raise them.
**Meta figure and diagram explanations:**
> NO: "This diagram lists the sensor stack of a humanoid robot. With it in view, the previous problems become easier to place."
> NO: "I made this diagram with ChatGPT Image2. Seeing the representations side by side makes the differences easier to grasp."
> NO: "This timeline shows the evolution... That is one of the reasons I find this field more interesting..."
> OK: The image or timeline itself. Let the surrounding judgment or personal project anchor carry the weight. Keep creation-process details only if they are themselves part of the story.
**Re-anchoring after cutting recaps (long-form articles):**
Keep concrete project details when cutting recaps, but do not add another callback to the same project at every section ending. A callback earns its place only when it adds a consequence or limitation not already explained.