From e093ee599d20b5ca110d9d5f9bbb90fdc5a9d9f6 Mon Sep 17 00:00:00 2001
From: buttercat1791 <mjjurkoic@gmail.com>
Date: Tue, 29 Jul 2025 14:28:44 -0500
Subject: [PATCH] Give explicit instructions on reading and updating anchor
 comemnts

---
 .cursor/rules/alexandria.mdc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.cursor/rules/alexandria.mdc b/.cursor/rules/alexandria.mdc
index 61e8b28..15ee6d0 100644
--- a/.cursor/rules/alexandria.mdc
+++ b/.cursor/rules/alexandria.mdc
@@ -54,6 +54,8 @@ NEVER assume developer intent. If you are unsure about something, ALWAYS stop an
 
 ### General Guidance
 
+- Before writing any code, ALWAYS search the codebase for relevant anchor comments.
+- Whenever updating code, ALWAYS update relevant anchor comments.
 - Prefer to use Deno to manage dependencies, build the project, and run tests.
 - Use snake_case names for plain TypeScript files.
 - Use comments sparingly; aim to make code readable and self-documenting.