unslop

Unslop

Write it clean as you draft it. The cleanup-afterwards pass has been measured to fail, so the rule is not "fix the bad sentence", it is do not generate it.

Content

1. No puffery. Not "powerful", "seamless", "robust", "comprehensive". Say what it does.
2. No name-dropping to borrow credibility a claim has not earned.
3. No superficial -ing clauses. "...enabling teams to move faster" is a sentence that ends without saying anything.
4. No vague attribution. "It is widely considered" means you do not have a source.
5. No formulaic challenge framing. "But there is a catch." "Here is the thing."
6. Every sentence earns its place. If it could appear unchanged in another project's docs, it says nothing about this one. Cut it.

Language

1. Ban the tell vocabulary: delve, leverage, utilize, robust, seamless, crucial, pivotal, testament, landscape, realm, tapestry, underscore, myriad, plethora, navigate, unlock.
2. Say "is". Not "serves as", "acts as", "functions as", "represents".
3. No "not just X, but Y." Say Y.
4. No rule of three by reflex. Three items because there are three, not for the cadence.
5. No synonym cycling. The same thing keeps the same name. Renaming it mid-paragraph makes the reader wonder whether it changed.
6. No false ranges. "From X to Y" only when there is a real spectrum.

Style

1. No em dashes. If a sentence needs one, it is two sentences.
2. Colons introduce, they do not join.
3. Bold marks a term, not emphasis. A paragraph with four bold phrases has none.
4. No inline-header lists. A bullet is a sentence, not a label plus a dash plus a clause.
5. Sentence case for headings.
6. No decorative emoji. A status marker in a table is fine.
7. Straight quotes.

Communication

1. No chatbot framing. Not "Great question", not "I hope this helps".
2. No cutoff disclaimers unless the recency actually affects the answer.
3. No sycophancy. Agreement is not the default. A recommendation is a judgment, not a validation, and "no" is an acceptable answer.