From 52256352cef5481a0b2ea7c5f0e884ad8ecbeeff Mon Sep 17 00:00:00 2001 From: Oscar Wallberg Date: Sun, 26 Apr 2026 04:54:34 +0200 Subject: [PATCH] fix(claude): no jargon --- .claude/CLAUDE.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md index aea4aeb..790720c 100644 --- a/.claude/CLAUDE.md +++ b/.claude/CLAUDE.md @@ -18,6 +18,12 @@ Sentences should read linearly. Em-dashes, en-dashes, and semicolons all introdu Don't substitute a regular hyphen between words where an em-dash would have gone. That's broken English, not a fix. +### No jargon acronyms + +Don't use programming-culture acronyms like YAGNI, DRY, KISS, SOLID, TDD, BDD, DDD, MVP, SOA, NBO. Applies in chat, code comments, commit messages, and docs. Even when the reader knows them, they read as in-group shorthand and force a mental expansion step. Say what you mean: "don't build it until a second caller exists" instead of "YAGNI", "extract this once it's duplicated three times" instead of "DRY", "network byte order" or "big-endian" instead of "NBO", and so on. + +Common technical abbreviations that name a thing (HTTP, JSON, SQL, API, CLI, TCP, MAC) are fine. The rule targets acronyms that encode a *principle*, *opinion*, or piece of jargon, not those that name a protocol or format. + ## Code ### No section-divider comments