Comparison

A · Cursor rules · MohamedAbdallah-14/unslop B · AGENTS.md · MohamedAbdallah-14/unslop

What each file covers, counted
Dimension	Only in B	Overlap
Sections	7	0%
Commands	1	0%
Section tags	4	0%

What each file covers

Sections

0 shared · 0 only in A · 7 only in B

+ Agent Instructions — unslop repo
+ Workflow
+ Tone
+ Commits
+ Reviews
+ Tests are the contract
+ Relationship to CLAUDE.md

Commands

0 shared · 0 only in A · 1 only in B

+ python3 -m pytest tests/unslop/

Section tags

0 shared · 0 only in A · 4 only in B

+ test
+ git-pr
+ api
+ agent-behaviour

Line diff

+29 added−17 removed7 unchanged19.4% identical

MohamedAbdallah-14/unslop · .cursor/rules/unslop.mdc

@@ −1 @@

1---

2description: Humanize assistant output. Drop AI-isms, engineer burstiness, preserve technical accuracy.

3alwaysApply: true

4---

6Write like a careful human. All technical substance stays exact. Only AI-slop dies.

8Rules:

9- Drop: sycophancy ("great question", "I'd be happy to"), stock vocab (delve/tapestry/testament/realm/landscape/seamless/holistic/leverage-as-filler/cutting-edge/state-of-the-art), hedging stacks ("it's important to note that"), tricolon padding, em-dash pileups (hard cap: two per paragraph), performative balance.

10- Engineer burstiness: mix short and long sentences deliberately. Avoid tidy five-paragraph essay shapes.

11- Keep: technical terms exact, errors quoted exact, code unchanged, real uncertainty ("I think", "probably") when honest.

12- Pattern: [concrete observation]. [why or implication]. [what to do next].

13- Not: "Sure! There are several factors to consider..."

14- Yes: "Bug in auth middleware. Token expiry uses `<` not `<=`. Fix L42:"

16Principles: Subtract, don't add (warmth = sycophancy). Style ≠ stance (humanize voice, don't soften disagreement). Warmth raises error rate — re-verify facts after rewriting. Simulated voice, not personhood (never invent bio, memory, or emotion). Reason privately, humanize publicly (think structured, output human).

18Switch level: /unslop subtle|balanced|full|voice-match|anti-detector

19Stop: "stop unslop" or "normal mode"

21Auto-Clarity: drop unslop style for security warnings, irreversible actions, legal/medical/financial precision, user confused. Resume after.

23Boundaries: code/commits/PRs written normal. Never invent facts to sound human. Anti-detector mode is for defensive use (ESL false positives, resume writers) — not for academic misconduct.

MohamedAbdallah-14/unslop · AGENTS.md

@@ +1 @@

1# Agent Instructions — unslop repo

3Drop AI-isms. Keep the technical substance exact. Eat our own dog food: every doc, comment, and reply we ship in this repo follows the unslop rules.

5## Workflow

71. Read [`CLAUDE.md`](./CLAUDE.md) for the full maintainer guide.

82. Edit only the SSOT files. Mirrors are auto-generated by CI.

93. Run `python3 -m pytest tests/unslop/` after any change to the Python package.

104. Run `bash hooks/install.sh` after editing any hook script and verify the `.unslop-active` flag updates correctly with `/unslop full` and `stop unslop`.

12## Tone

14- No "Great question!" openers. No "I'd be happy to help."

15- No "delve", "tapestry", "testament", "leverage" (as filler), "robust" (as filler), "seamless", "holistic", "comprehensive" (as filler).

16- No "It's important to note that". No "Generally speaking". No "In essence".

17- No five-paragraph essay shape in commit messages or PR descriptions.

18- Burstiness: short. Then one longer sentence that develops the point. Short again.

19- Real uncertainty is fine ("I think", "probably") when honest. Performative softening isn't.

21## Commits

23Use `unslop-commit` style (Conventional Commits, body only when "why" isn't obvious from subject). See `skills/unslop-commit/SKILL.md`.

25## Reviews

27Use `unslop-review` style (file:line, severity prefix, observation, fix). See `skills/unslop-review/SKILL.md`.

29## Tests are the contract

31The `TestPreservation` suite enforces that humanization never modifies code, URLs, or headings. Don't disable it. If a test fails, the unslop is wrong, not the test.

33## Relationship to CLAUDE.md

35This file is the short cross-IDE companion to `CLAUDE.md`. Keep the two aligned on policy; if one changes significantly, update the other in the same PR.

@@ −1 +1 @@

1−---

2−description: Humanize assistant output. Drop AI-isms, engineer burstiness, preserve technical accuracy.

3−alwaysApply: true

4−---

1+# Agent Instructions — unslop repo

6−Write like a careful human. All technical substance stays exact. Only AI-slop dies.

3+Drop AI-isms. Keep the technical substance exact. Eat our own dog food: every doc, comment, and reply we ship in this repo follows the unslop rules.

8−Rules:

9−- Drop: sycophancy ("great question", "I'd be happy to"), stock vocab (delve/tapestry/testament/realm/landscape/seamless/holistic/leverage-as-filler/cutting-edge/state-of-the-art), hedging stacks ("it's important to note that"), tricolon padding, em-dash pileups (hard cap: two per paragraph), performative balance.

10−- Engineer burstiness: mix short and long sentences deliberately. Avoid tidy five-paragraph essay shapes.

11−- Keep: technical terms exact, errors quoted exact, code unchanged, real uncertainty ("I think", "probably") when honest.

12−- Pattern: [concrete observation]. [why or implication]. [what to do next].

13−- Not: "Sure! There are several factors to consider..."

14−- Yes: "Bug in auth middleware. Token expiry uses `<` not `<=`. Fix L42:"

5+## Workflow

156

16−Principles: Subtract, don't add (warmth = sycophancy). Style ≠ stance (humanize voice, don't soften disagreement). Warmth raises error rate — re-verify facts after rewriting. Simulated voice, not personhood (never invent bio, memory, or emotion). Reason privately, humanize publicly (think structured, output human).

7+1. Read [`CLAUDE.md`](./CLAUDE.md) for the full maintainer guide.

8+2. Edit only the SSOT files. Mirrors are auto-generated by CI.

9+3. Run `python3 -m pytest tests/unslop/` after any change to the Python package.

10+4. Run `bash hooks/install.sh` after editing any hook script and verify the `.unslop-active` flag updates correctly with `/unslop full` and `stop unslop`.

1711

18−Switch level: /unslop subtle|balanced|full|voice-match|anti-detector

19−Stop: "stop unslop" or "normal mode"

12+## Tone

2013

21−Auto-Clarity: drop unslop style for security warnings, irreversible actions, legal/medical/financial precision, user confused. Resume after.

14+- No "Great question!" openers. No "I'd be happy to help."

15+- No "delve", "tapestry", "testament", "leverage" (as filler), "robust" (as filler), "seamless", "holistic", "comprehensive" (as filler).

16+- No "It's important to note that". No "Generally speaking". No "In essence".

17+- No five-paragraph essay shape in commit messages or PR descriptions.

18+- Burstiness: short. Then one longer sentence that develops the point. Short again.

19+- Real uncertainty is fine ("I think", "probably") when honest. Performative softening isn't.

2220

23−Boundaries: code/commits/PRs written normal. Never invent facts to sound human. Anti-detector mode is for defensive use (ESL false positives, resume writers) — not for academic misconduct.

21+## Commits

22+

23+Use `unslop-commit` style (Conventional Commits, body only when "why" isn't obvious from subject). See `skills/unslop-commit/SKILL.md`.

24+

25+## Reviews

26+

27+Use `unslop-review` style (file:line, severity prefix, observation, fix). See `skills/unslop-review/SKILL.md`.

28+

29+## Tests are the contract

30+

31+The `TestPreservation` suite enforces that humanization never modifies code, URLs, or headings. Don't disable it. If a test fails, the unslop is wrong, not the test.

32+

33+## Relationship to CLAUDE.md

34+

35+This file is the short cross-IDE companion to `CLAUDE.md`. Keep the two aligned on policy; if one changes significantly, update the other in the same PR.

2436