Unslop text

Rewrite prose so a technical reader can follow it. Preserve meaning and verdicts. Do not restructure code. Do not add soul.

For orchestrated cleanup of a git branch (TypeScript, Zod, shims, location, then this pass on comments/docs in the diff), use unslop-code.

Length is not the metric

Cut redundancy. Spend the saved words on the thing the reader does not know yet. Never pad. Never answer "what is this" with a label. If the reader would have to search the web to follow a sentence, explain it in place.

Never trade a fact for a smoother sentence

Grok's prose is often hard to read and still precise. Keep every version number, file path, script name, verdict, and threshold. If a smooth sentence loses "only dev:vite passes --bun", the smooth sentence is wrong.

Keep the anchors. Cite the file ([util.ts](app/src/…/util.ts)), a pinned permalink, or a line-range code block so the reader can check the claim.

Shape

Open with where we are, or what the thing is. Then one section per option. Put a visible verdict on each option (do now / try / later / don't, or a one-line recommendation) plus the reason.