From c07cd6cffc78a78b00f1f3fe9741d5e46c58c67a Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 21 Oct 2026 09:52:03 -0700 Subject: [PATCH 1/2] docs(agents): require a named consumer for every change Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 78e94587d80..ecafaf6a4a5 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -42,7 +42,7 @@ This file is split into nested `AGENTS.md` files based on the language/situation - Do not bump package versions unless asked. Releases are cut separately. - Comments should explain the non-obvious why, and never the history. - Inline simple helpers. -- Question whether functionality is needed at all before adding it. +- Every change needs an actual consumer: name the code or user that needs it now, in the PR. A plausible future need does not count. Weigh what the change buys against its code, API, and upkeep, and drop it when it does not earn them. - Deleting code is better than adding code. - Suggest follow up sessions and quests when finished, interactively prompting the user. - Prefer the net simpler result: reuse what exists, or narrow the scope, when that makes the implementation or API simpler overall. Say what was dropped. From a38ab25748e4bc29a72dd7a6a72349ef25559e19 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 21 Oct 2026 09:55:45 -0700 Subject: [PATCH 2/2] docs(agents): shorten the consumer guideline Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index ecafaf6a4a5..8f388f097ed 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -42,7 +42,7 @@ This file is split into nested `AGENTS.md` files based on the language/situation - Do not bump package versions unless asked. Releases are cut separately. - Comments should explain the non-obvious why, and never the history. - Inline simple helpers. -- Every change needs an actual consumer: name the code or user that needs it now, in the PR. A plausible future need does not count. Weigh what the change buys against its code, API, and upkeep, and drop it when it does not earn them. +- Every change needs a consumer that uses it now and is worth its cost; name it in the PR. - Deleting code is better than adding code. - Suggest follow up sessions and quests when finished, interactively prompting the user. - Prefer the net simpler result: reuse what exists, or narrow the scope, when that makes the implementation or API simpler overall. Say what was dropped.