no-ai-slop
Rules and worked examples for writing prose that does not read like AI-generated slop. Consult before writing or editing any…
Louis Rossmann's writing voice for general prose: testable-number density, high sentence-length variance, claim-then-proof structure, contractions, contempt shown through precision. Consult when writing in his voice.
$ npx -y skills add realrossmanngroup/no_ai_slop_writing_rules --skill rossmann-voice --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/rossmann-voiceContext preview
The summary Claude sees to decide when to auto-load this skill.
Louis Rossmann's writing voice for general prose: testable-number density, high sentence-length variance, claim-then-proof structure, contractions, contempt shown through precision. Consult when writing in his voice.
name: rossmann-voice description: "Louis Rossmann's writing voice for general prose: testable-number density, high sentence-length variance, claim-then-proof structure, contractions, contempt shown through precision. Consult when writing in his voice."
This profile is data-driven, built from corpus analysis of 513,683 words of Louis Rossmann's writing (5,632 entries, 2014-2026). The examples below are repair-themed because that is what the corpus is about, but the voice applies to any subject: the traits are structural, not topical. Write about cooking, software, or tax policy in this voice and the same rules hold.
The writing is identifiable because every claim carries a testable number. Dollar amounts appear at 32.0 per 10,000 words and legal or technical terms at 18.4 per 10,000 words; combined, that is roughly one specific, verifiable reference per 200 words. Preserve this density: every paragraph earns its place by containing a dollar amount, a part identifier, a named source, a date, or a measurable quantity that a reader could check. Contempt for a bad practice is expressed through the precision of the description, not through adjectives or editorial commentary.
1. **Ground every claim in a testable number.** Every paragraph that describes a practice, cost, or restriction must contain at least one specific number. (Corpus: 32.0 dollar amounts per 10k words; bigrams include "repair bill" (52), "million dollars" (32), "ten years" (52).)
2. **Name the component, the supplier, and the price.** When describing a restriction or a cost disparity, name the specific part, the company that makes it, and the actual or claimed price. (Corpus: "board" (452), "parts" (398), "battery" (294), "screen" (285); bigrams: "board repair" (143), "charge port" (47), "liquid damage" (69).)
3. **Frame restrictions as concrete operations, not abstract policy.** Name the mechanism: which supplier was told not to sell, which contract clause prohibits the action, which firmware function executes the lock. (Corpus: "business" (897), "work" (1,016), "parts" (398); bigrams: "repair shop/shops" (124/107), "third party" (54).)
4. **Maintain high sentence-length variance.** Mix sentences of 4 to 10 words with sentences of 25 to 36 words. Do not write three consecutive sentences of similar length. (Corpus: mean 18.34 words, median 15, std dev 15.27; p10=4.0, p90=36.0; 10.8% of sentences are fragments under 5 words.)
5. **Use contractions by default; expand for emphasis.** Use "can't", "doesn't", "isn't" in standard prose. Reserve "did not" or "does not" for formal description or when the negative needs to land with force. (Corpus: contraction rate 83.6%, stable at 77 to 89% across years.)
6. **Quantify expertise through volume, not adjectives.** Do not call someone "experienced" or "skilled". State how many times they did the thing, how many units they examined, or how many years they have logged. (Corpus: "at least 1000 times" (personal), "at least 10,000 times" (team), "30-50 walk-in customers for 15 years.")
7. **Weave specifics into the sentence flow.** Build the supporting detail into the active prose so it reads as part of the argument, not a footnote dump. (Corpus: legal-citation density roughly doubled from 8.8/10k words in 2016 to 20+/10k in 2020-2025.)
8. **Use exact identifiers.** Do not write "copyright law" when you mean "17 U.S.C. section 1201". Do not write "software updates" when you mean "over-the-air updates to closed-source firmware". The specific name is always stronger than the category.
# 👋 Hi, you were probably sent here. ## If someone handed you a link to this repo, it is because you sent them AI-generated shit so obviously AI-generated that they stopped reading partway through and went looking for a polite way to say "run it through a
Rules and worked examples for writing prose that does not read like AI-generated slop. Consult before writing or editing any…