From 6562b20ee545d2b36e311e48ac67b936a9eb31ad Mon Sep 17 00:00:00 2001 From: John O'Keefe Date: Fri, 27 Feb 2026 16:57:41 -0500 Subject: [PATCH] docs: add code indentation guideline to project standards Add explicit guideline specifying 2-space indentation for all code files unless the language prohibits it. This ensures consistent formatting across the entire codebase and prevents debates about tab vs space preferences. The guideline is placed in the General section alongside other coding convention rules to maintain consistency in project standards. --- PROJECT_GUIDELINES.md | 1 + 1 file changed, 1 insertion(+) diff --git a/PROJECT_GUIDELINES.md b/PROJECT_GUIDELINES.md index 478c36f..0da0f26 100644 --- a/PROJECT_GUIDELINES.md +++ b/PROJECT_GUIDELINES.md @@ -55,6 +55,7 @@ - Run `git push` and wait for completion - Never use `&&` to chain git commands together - ✅ **Make good organized git commits for the entire project (not just what you changed) and push - run git add, commit, push sequentially as separate commands, no need to repeatedly check status** +- ✅ **Indentation is always 2 spaces unless the language prohibits it** ### Cascading Fix-up Pattern (PROHIBITED)