From 2c0fd4f86b011bbc8c0d86c61f96ade3ea249508 Mon Sep 17 00:00:00 2001
From: Maze Winther <mazewinther@gmail.com>
Date: Wed, 25 Mar 2026 16:16:42 +0100
Subject: untrack .cursor/

---
 .cursor/rules/comments.mdc | 34 ----------------------------------
 1 file changed, 34 deletions(-)
 delete mode 100644 .cursor/rules/comments.mdc

(limited to '.cursor/rules/comments.mdc')

diff --git a/.cursor/rules/comments.mdc b/.cursor/rules/comments.mdc
deleted file mode 100644
index 4b9180cf..00000000
--- a/.cursor/rules/comments.mdc
+++ /dev/null
@@ -1,34 +0,0 @@
----
-alwaysApply: false
----
-# Comment Guidelines
-
-## Good Comments (Human-style)
-- Explain WHY, not WHAT
-- Document non-obvious behavior or edge cases
-- Warn about performance implications or side effects
-- Explain business logic that isn't clear from code
-
-Examples:
-```javascript
-// transfer, not copy; sender buffer detaches
-// satisfies: check shape; keep literals  
-// keep multibyte across chunks
-// timingSafeEqual throws on length mismatch
-```
-
-## Bad Comments (AI-style)
-- Don't explain what the code literally does
-- Don't add changelog-style comments in code
-- Don't comment every line or obvious operations
-
-Avoid:
-```javascript
-// Prevent duplicate initialization
-// Check if project is already loaded  
-// Mark as initializing to prevent race conditions
-// (changed from blah to blah)
-```
-
-## Rule
-Only add comments when there's genuinely non-obvious behavior, performance considerations, or business logic that needs context. Code should be self-documenting through naming and structure.
\ No newline at end of file
-- 
cgit v1.3.1