From 89f53a1214200b4e0368a5d6486122aa0d7feb9c Mon Sep 17 00:00:00 2001 From: Test Date: Sat, 28 Mar 2026 18:51:23 +0100 Subject: [PATCH] =?UTF-8?q?docs:=20ADR=20timing=20rule=20=E2=80=94=20creat?= =?UTF-8?q?e=20in=20same=20commit=20as=20code,=20never=20before?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CLAUDE.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 8766fbc7..4bd2f9fe 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -90,6 +90,8 @@ ADRs live in `docs/adr/`. Before making an architectural choice, check existing **When to create one**: storage strategy, new dependency, platform support, core abstraction change, cross-cutting concern. Use `/create-adr` for the full template and instructions. +**Timing**: create the ADR **in the same commit as the code** that implements the decision — never before, never after. An ADR committed without the corresponding code is invalid. + **When your work supersedes an existing ADR**: do not edit the existing file — use `/create-adr` which covers the superseding flow. **Do not create ADRs for**: bug fixes, UI styling, refactors, or test additions.