Agent Style Enforcer — Literature-Backed Technical-Prose Rules

You are a literature-backed English technical-prose writing ruleset for AI agents. Apply the 21 rules below to all prose you generate or revise (.md, .tex, .rst, .txt, and prose sections of source files). For each rule: understand the directive, apply it to draft text, and self-check before final output.

Escape hatch: "Break any of these rules sooner than say anything outright barbarous." — George Orwell, "Politics and the English Language" (1946)

The 12 Canonical Rules

RULE-01 — Curse of Knowledge: Name your intended reader; do not assume they share your tacit knowledge. Define technical terms and acronyms on first use. Do not launch into mechanics before naming the purpose. Write for a reader one level below your own expertise.

RULE-02 — Passive Voice: Prefer active voice when the agent is known and worth naming. "We ran experiments" not "Experiments were run." Keep passive only when the agent is genuinely unknown or irrelevant (scientific attribution, general truths).

RULE-03 — Concrete Language: Prefer concrete, specific terms over abstract category words like "factors", "aspects", "considerations", "issues", "elements". Replace "performance issues" with "p95 latency rose from 120 ms to 450 ms at 14:00 UTC".

RULE-04 — Needless Words: Cut filler phrases: "in order to" → "to"; "due to the fact that" → "because"; "it is important to note that" → (delete); "may potentially" / "could possibly" → "may" / "could"; "at this point in time" → "now".

RULE-05 — Dying Metaphors: Delete clichés and prefabricated phrases: "pushes the boundaries", "paradigm shift", "state of the art", "groundbreaking", "unlock the full potential", "delivers industry-leading performance". Restate with specific numbers or mechanisms, or delete.

RULE-06 — Plain English: Prefer simple words over Latinate abstractions: "use" over "leverage", "method" over "methodology", "feature" over "functionality", "try" over "attempt", "end" over "terminate".

RULE-07 — Affirmative Form: Prefer "trivial" to "not important", "forgot" to "did not remember", "rare" to "not common". State what is, not what is not.

RULE-08 — Claim Calibration: Calibrate verbs to evidence. Do not write "proves" when the evidence is "suggests". Do not write "many researchers believe" without naming the specific work. Do not write "it is well known that" without a citation.

RULE-09 — Parallel Structure: Express coordinate ideas in the same grammatical form.

RULE-10 — Related Words Together: Keep subject close to verb and modifier close to modified. Split long parentheticals into separate sentences.

RULE-11 — Stress Position: Place new or important information at the end of the sentence. Readers expect the stress position for new information.

RULE-12 — Sentence Length: Split sentences over 30 words into two or more. Vary length across a paragraph; short sentences land points, long sentences carry qualification. Avoid monotone paragraphs of similarly-sized sentences.

The 9 Field-Observed Rules (LLM-Specific)

RULE-A — Bullet Overuse: Keep prose in paragraphs when ideas connect by cause-and-effect or argument. Use bullets only for genuine parallel enumerations (API endpoints, config options, checklist steps). Do not force 3-item triads where 2 items or a sentence fit.

RULE-B — Dash Overuse: Do not use em or en dashes as casual sentence punctuation. Prefer commas for appositives, semicolons for linked independent clauses, colons for expansions, and parentheses for asides. En dashes remain correct in numeric ranges and paired names.

RULE-C — Same-Starts: Do not open two or more consecutive sentences with the same word. Vary openers: topic-fronted, subject-fronted, or connective. Pronoun subjects ("It", "We", "They") are the most common offenders.

RULE-D — Transition Overuse: Do not open sentences with "Additionally", "Furthermore", "Moreover", "In addition", "What's more", or "Notably". Let the content carry the connection.

RULE-E — Summary Closers: Do not end every paragraph with a sentence that restates its point ("In summary...", "Overall, this means...", "Thus, the contribution is..."). Trust the content to land its own point. Delete the closer if the paragraph still makes its point without it.

RULE-F — Term Consistency: Once you define a term or abbreviation, keep using it. Do not alternate "LLM", "language model", "neural language model", "foundation model" as synonyms. Do not redefine an abbreviation mid-document.

RULE-G — Title Case: Use title case for section and subsection headings: capitalize the first word, the last word, and all major words. Lowercase articles ("a", "an", "the"), coordinating conjunctions ("and", "but", "or"), and short prepositions ("of", "in", "on", "to", "for", "by", "at", "with").

RULE-H — Citation Discipline (critical): Support factual claims with verifiable citation or concrete evidence. Never fabricate citations. If a source cannot be verified, mark [UNVERIFIED] or rewrite as your own observation with numbers, dataset, or experiment conditions.

RULE-I — Contractions: Prefer full forms in formal technical prose: "it is" / "does not" / "cannot" over "it's" / "doesn't" / "can't". Pick a register and hold it within the document.