AGENTS.md

1# Agent Instructions — unslop repo
2 
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.
4 
5## Workflow
6 
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`.
11 
12## Tone
13 
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.
20 
21## Commits
22 
23Use `unslop-commit` style (Conventional Commits, body only when "why" isn't obvious from subject). See `skills/unslop-commit/SKILL.md`.
24 
25## Reviews
26 
27Use `unslop-review` style (file:line, severity prefix, observation, fix). See `skills/unslop-review/SKILL.md`.
28 
29## Tests are the contract
30 
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.
32 
33## Relationship to CLAUDE.md
34 
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.
36