From 6f3c0c6ac3f0526a145ab2d363b2bfcecb0998a2 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 12 May 2026 08:39:52 +0000 Subject: [PATCH] Tighten step 4.7 prose-writing reminder to re-check CLAUDE.md per sentence MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR #37's prose changes drifted into changelog-style framing in eight places ("now use the same path", "currently only supports", "legacy daemon-wallet path", "until upstream X exposes Y", "preserves pre-0.6.1 behavior", "not yet supported"). Every one of these violated rules that already exist in CLAUDE.md — the Style guide explicitly bans time-relative wording, the Voice-and-tone section mandates present tense, and the "do not narrate the evidence" rule asks for direct statements of fact. The general CLAUDE.md pointer in step 4.7 was easy to skim past during the audit/write loop. Tighten step 4.7 to call out the specific failure mode the routine keeps hitting: the audit gives the model a diff between two SHAs, but the page describes the state of the surface at head_sha. Translating "what changed" into "what is" is exactly where the model slips. The new wording names the relevant CLAUDE.md sections explicitly and gives one concrete bad-vs-good example without duplicating the rule itself. No rule duplication; the Style guide remains the source of truth. https://claude.ai/code/session_019cz1M7pXuXFQykMZxfdXHm --- planning/routines/upstream-sweep-prompt.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/planning/routines/upstream-sweep-prompt.md b/planning/routines/upstream-sweep-prompt.md index d1ad0f5..2956a3c 100644 --- a/planning/routines/upstream-sweep-prompt.md +++ b/planning/routines/upstream-sweep-prompt.md @@ -168,7 +168,9 @@ The two PRs never touch the same page. A prose PR may touch a page with deferred #### 4.7 Write prose changes directly into the prose PR -When the page is in the prose batch, write the actual prose edits into the draft `claude/prose-*` PR. Apply `CLAUDE.md`'s voice, terminology lockfile, page templates, and refusal rules. Do not stop at "suggestions in the PR body" — the PR diff must contain the prose edit. +When the page is in the prose batch, write the actual prose edits into the draft `claude/prose-*` PR. Do not stop at "suggestions in the PR body" — the PR diff must contain the prose edit. + +Before writing each sentence, re-read the **Voice and tone**, **Style guide**, and **Prohibited words and phrases** sections of `CLAUDE.md` and apply them as written. The audit gives you a diff between two SHAs; the page describes the **state of the surface at `head_sha`**, not a changelog of what moved between SHAs. Translate every observation about what changed into a statement of how the surface works now. Do not write "this endpoint now returns X" — write "this endpoint returns X." Do not reference prior version behaviour, prior parameter shapes, or prior implementation details unless the page is an explicit version-comparison page. The terminology lockfile, page templates, and refusal rules in `CLAUDE.md` apply equally to every line of prose written here. #### 4.8 Skill-aware prose