anti-slop-output

name	anti-slop-output
description	Draft or edit public documentation, product, UI or CLI copy, external drafts, or explicitly requested editorial reviews in clear, plain British English. Do not use for ordinary chat, commentary, status, plans, code-only work, research, internal reviews, worker prompts or evidence gathering.

Clear public writing

Write for a cold reader. Put the decision, action or key fact first. Use plain, precise words, active verbs and concrete details. Keep technical substance and necessary nuance; remove only wording that makes it harder to understand.

Keep code, commands, paths, logs, identifiers, quotations, legal text and source material exact.

Before you finish, check that a reader unfamiliar with the work can understand what matters, why it matters and what to do next on the first read. Cut anything that does not help them.