Skip to content

docs: record the brevity rule in CLAUDE.md #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
serpeigd merged 1 commit into from
Aug 14, 2026
Merged

docs: record the brevity rule in CLAUDE.md #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -263,6 +263,12 @@ design decision.
- Ground truth is LLM-researched-with-citations, not hand-labeled — say so precisely;
never call it "hand-labeled."
- `run_eval.py` blocks below 15 labeled titles by design — don't lower the threshold.
- **Keep it short (2026-08-13, explicit request in chat).** Too much text, too much
explaining. Lead with the answer or the change; give reasoning only where it would
change a decision. Don't recap work already visible in the diff, don't restate the
question before answering it, and don't close with a summing-up line. Applies to
chat, commit messages and PR bodies. Reference docs (README, this file) can be
longer, but only where the length earns it.
- Never report leakage_rate/grounded_fact_rate without richness alongside — an empty
output scores perfectly on the first two.
- New generators get tested against fixtures/`ScriptedFakeGenerator` first, never the
Expand Down
Loading