From dbacb1cd010e7ad96eea1f815bb59fb47a3c0b8b Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Wed, 18 Mar 2026 06:05:13 -0700 Subject: [PATCH] docs: exclude internal details from CHANGELOG style guide Co-Authored-By: Claude Opus 4.6 (1M context) --- CLAUDE.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 0979c95e..44247ce5 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -141,6 +141,8 @@ CHANGELOG.md is **for users**, not contributors. Write it like product release n - Lead with what the user can now **do** that they couldn't before. Sell the feature. - Use plain language, not implementation details. "You can now..." not "Refactored the..." +- **Never mention TODOS.md, internal tracking, eval infrastructure, or contributor-facing + details.** These are invisible to users and meaningless to them. - Put contributor/internal changes in a separate "For contributors" section at the bottom. - Every entry should make someone think "oh nice, I want to try that." - No jargon: say "every question now tells you which project and branch you're in" not