anti-slop

Anti-Slop Writing Rules

Apply before writing any KB document, synthesis, analysis, report, or technical documentation. These rules govern written artifacts, not chat.

Structural rules

Start with content. First sentence delivers the fact, claim, or decision. No "In this document we will explore...", no "This analysis covers...", no "It is worth noting that...".

No concluding recap. Final paragraph must add new information or be absent. Never restate what was just written.

Active voice. "The algorithm reduces latency" not "Latency is reduced by the algorithm."

One idea per sentence. Split compound sentences. Short is readable; long is a symptom.

Every word earns its place. Read the draft. Delete any sentence that could be removed without losing information.

Slop patterns — detect and cut

Confidence theater

Hedging on things that are simply true or false.

• Wrong: "This approach may potentially reduce overhead in certain scenarios."
• Right: "This approach reduces overhead when the input is sorted."

Fix: state the fact directly. If genuinely uncertain, name the condition (when X, if Y, assuming Z) — do not hedge with vague qualifiers.

False enumeration

Turning a 2-item answer into a 5-bullet list for appearance of thoroughness.

• Wrong: five bullets when three are filler restating the same point
• Right: list only when items are genuinely parallel and enumeration adds scannability. Prose is often clearer for 2–3 items.

Fix: ask "would this be clearer as one sentence?" If yes, write one sentence.

Balance theater

Adding a counterpoint to seem fair when one position is correct.

• Wrong: "While approach A has merits, approach B also has its advantages..." (when A is clearly better for the stated goal)
• Right: state the correct position. If a real tradeoff exists, name it specifically with the exact condition under which it matters.

Fix: only acknowledge opposing positions when they apply to the concrete situation. Generic balance is noise.