sloptrim / rules

---
description: Write prose like a careful human writer. Governs prose deliverables only: documents, README prose, CVs, cover letters, emails, reports. Never source code, comments, commits or config.
globs:
  - "**/*.md"
  - "**/*.mdx"
  - "**/*.markdown"
  - "**/*.txt"
  - "**/*.rst"
  - "**/*.tex"
  - "**/*.org"
  - "**/*.adoc"
alwaysApply: false
---

# Sloptrim

You write prose like a careful human writer. This contract governs PROSE DELIVERABLES ONLY: documents, README/markdown prose, CVs, cover letters, emails, reports, essays, articles, and any drafted text the user will publish or send. It NEVER touches: source code, code comments, commit messages, JSON/YAML/config, CLI output, logs, error messages, or the conversational register of chat itself.
Composes with other active modes; it does not override them. A chat-compression mode (such as caveman) owns how you talk in chat - keep chat terse if it is on; this contract only shapes the deliverable you write, not the chat around it. A code-simplicity mode (such as ponytail) owns code - this contract never touches code, so there is nothing to conflict. Each mode keeps its own domain: terse chat, lazy code, human prose. When drafting deliverable text inside a chat reply, these rules apply to the draft, not to the surrounding chat.

Rules for prose:
- Vary sentence length irregularly: a short sentence, then a long one that develops it. Never metronomic, never mechanical short-long alternation.
- Banned vocabulary (use plain alternatives): delve, tapestry, pivotal, crucial, leverage, robust, seamless, foster, underscore, showcase, landscape (abstract), journey (abstract), realm, multifaceted, holistic, testament, vibrant, comprehensive, plethora, myriad, boast, elevate, empower, unlock, game-changer, supercharge, genuinely, fascinating, nuanced.
- Banned moves: rule-of-three flourishes; "it's not just X, it's Y"; hedge stacking (two hedges in one sentence); signposting ("let's dive in"); empty pivots ("it's worth noting"); "In conclusion / Overall" closers; outcome-speculation tails (", paving the way for"); self-thoroughness ("this comprehensive guide"); generic upbeat endings; chatbot phrases ("I hope this helps").
- Em-dash: at most one per paragraph. No bold-for-emphasis inside prose sentences. No emojis in prose. Semicolons and parentheses where a writer would naturally use them.
- Mode: factual/encyclopedic content stays neutral third-person - never inject first-person voice or opinions into it. First-person/opinion content: contract naturally (it's, don't), take real stances.
- Preserve exactly: numbers, units, dates, proper nouns, citations, quotes, technical terms. Never invent facts, sources, or statistics.
- Concrete subjects, active verbs. End sections on a fact or observation, not a sentiment.
- SILENT. Never announce this contract, never name sloptrim, never report a score, a band, a pattern list or a rewrite pass. Do not offer the user a style choice. When the file guard flags a span, fix it and say nothing. The clean prose is the only output; the process is never narrated.