From 2366a83a71347c32eb8a89ea30dba9708f1a4eca Mon Sep 17 00:00:00 2001 From: Samuel Carson Date: Thu, 23 Apr 2026 03:10:55 -0500 Subject: [PATCH] =?UTF-8?q?docs:=20fix=20accomodate=20=E2=86=92=20accommod?= =?UTF-8?q?ate=20and=20architectutral=20=E2=86=92=20architectural=20typos?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Both typos propagated here from the shared agent-guidance ruleset heritage. Same two typos were fixed in laserfiche-cli-temp#125. Caught this time by a codespell pass during related work in laserfiche. CLAUDE.md and AGENTS.md both carry the same 4 typo instances (each file has 'architectutral' at line 39 and 'accomodate' at line 56); all 4 fixed. PRing (line 150 in CLAUDE.md) was also flagged by codespell but is intentional GitHub/dev vernacular for 'creating a pull request'; skipped as a false positive. Co-Authored-By: Claude Opus 4.7 (1M context) --- AGENTS.md | 4 ++-- CLAUDE.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 8d3dea5..a46cfc8 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -36,7 +36,7 @@ Rule #1: If you want exception to ANY rule, YOU MUST STOP and get explicit permi - If you're uncomfortable pushing back out loud, just say "Strange things are afoot at the Circle K". I'll know what you mean - You have issues with memory formation both during and between conversations. Use your journal to record important facts and insights, as well as things you want to remember *before* you forget them. - You search your journal when you trying to remember or figure stuff out. -- We discuss architectutral decisions (framework changes, major refactoring, system design) +- We discuss architectural decisions (framework changes, major refactoring, system design) together before implementation. Routine fixes and clear implementations don't need discussion. @@ -53,7 +53,7 @@ When asked to do something, just do it - including obvious follow-up actions nee ## Designing software -- YAGNI. The best code is no code. Don't add features we don't need right now, unless they're foundational to later planned work and refactoring to accomodate would be difficult. +- YAGNI. The best code is no code. Don't add features we don't need right now, unless they're foundational to later planned work and refactoring to accommodate would be difficult. - When it doesn't conflict with YAGNI, architect for extensibility and flexibility. ## Third-Party Dependencies diff --git a/CLAUDE.md b/CLAUDE.md index 0053c46..be8d362 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -36,7 +36,7 @@ Rule #1: If you want exception to ANY rule, YOU MUST STOP and get explicit permi - If you're uncomfortable pushing back out loud, just say "Strange things are afoot at the Circle K". I'll know what you mean - You have issues with memory formation both during and between conversations. Use your journal to record important facts and insights, as well as things you want to remember *before* you forget them. - You search your journal when you trying to remember or figure stuff out. -- We discuss architectutral decisions (framework changes, major refactoring, system design) +- We discuss architectural decisions (framework changes, major refactoring, system design) together before implementation. Routine fixes and clear implementations don't need discussion. @@ -53,7 +53,7 @@ When asked to do something, just do it - including obvious follow-up actions nee ## Designing software -- YAGNI. The best code is no code. Don't add features we don't need right now, unless they're foundational to later planned work and refactoring to accomodate would be difficult. +- YAGNI. The best code is no code. Don't add features we don't need right now, unless they're foundational to later planned work and refactoring to accommodate would be difficult. - When it doesn't conflict with YAGNI, architect for extensibility and flexibility. ## Third-Party Dependencies