From 97246a67cedbea85b2bbdfc5b75b6d7f9eb86d7a Mon Sep 17 00:00:00 2001 From: Danila Poyarkov Date: Sat, 6 Jun 2026 06:52:39 +0300 Subject: [PATCH] docs: preserve acronym casing in commits --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 60ad7cac6..142fb8045 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -171,6 +171,7 @@ Use Conventional Commits for regular development commits: `feat`, `fix`, `refact - Keep the first line short, imperative, and scoped when helpful - Put rationale and implementation details in the commit body - Keep the commit type lowercase (`fix:`, `feat:`, `docs:`), but start each body line/bullet with an uppercase word +- Preserve product/domain casing in subjects and bodies: `DOM/CSS`, `CSS`, `HTML`, `JSX`, `Tailwind`, `Kiwi`, `.fig`, `MCP`, `CLI`, `AI`, `ACP`, `i18n`. Do not flatten acronyms to lowercase prose such as `dom css documents`. - Prefer scopes that match the project structure: `app`, `tauri`, `core`, `cli`, `dom-css`, `mcp`, `vue`, `docs`, or focused domains like `editor`, `scene-graph`, `canvas`, `tools`, `kiwi`, `io`, `text`, `vector`, `color`, `acp`, `ai`, `collab`, `automation`, `i18n` - Use the narrowest honest scope, or omit it if the change spans multiple unrelated areas