Update Cursor Project Rule Editor with Enhanced Formatting and Critical Warning

codekiln · codekiln · commit 2f34845d58b2 · 2025-03-03T07:00:19.000-05:00
- Refine `.mdc` file formatting guidelines
- Add critical warning about file initialization bug when creating/editing `.mdc` files
- Update description and globs configuration
- Improve frontmatter and link formatting recommendations
- Enhance rule documentation with more precise instructions
diff --git a/.cursor/rules/cursor-project-rule-editor.mdc b/.cursor/rules/cursor-project-rule-editor.mdc
@@ -1,12 +1,12 @@
 ---
-versionNum: 7a0e5aab
-description: How to Edit Cursor Rules and their appropriate location in the repository
-globs: 
+versionNum: b2fe3ee5
+description: Editing Cursor Project Rules
+globs: *.mdc
 source: https://gist.github.com/codekiln/242b572c64c1097277fd4c831db91c10
 ---
 # Cursor Project Rule Editor Rule
 
-`.mdc` files stand for Mark Down Cursor, and are meant to give the Cursor IDE AI Agent context on how to operate in the codebase.
+`.mdc` files stand for MarkDown Cursor, and are meant to give the Cursor IDE AI Agent context on how to operate in the codebase.
 This particular rule is about using the AI to author and edit `.mdc` files, so as to update the rules.
 This rule ensures `.mdc` files are correctly placed within a repository and adhere to standard formatting conventions.
 
@@ -61,11 +61,20 @@ actions:
          └── ...
          ```
 
-      4. Never place rule files:
+      4. VERY IMPORTANT - NEVER EVER place rule files:
          - In the project root
          - In subdirectories outside .cursor/rules
          - In any other location
 
+      5. ⚠️ CRITICAL WARNING - File Initialization Bug:
+         When the AI creates or edits a .mdc file, DO NOT open the file in the editor
+         until the changes are committed to the repository. There is currently a bug
+         where opening a newly created or edited .mdc file in the editor will cause
+         it to be initialized/erased. To avoid this:
+         - Wait for the AI to finish making changes
+         - Commit the changes to the repository
+         - Only then open the file in the editor if needed
+
 examples:
   - input: |
       # Bad: Rule file in wrong location
@@ -100,28 +109,32 @@ actions:
     message: |
       Markdown `.mdc` files should:
       
-      1. **Include a frontmatter block** at the top with a `description` field:
+      1. **Include a frontmatter block** at the top with `description` and `globs` fields:
          ```
          ---
-         description: "Description of the rule"
-         globs: "*.mdc"
+         description: <REQUIRED: RULE_DESCRIPTION_HERE>
+         globs: <OPTIONAL: COMMA_SEPARATED_GLOBS_HERE>
          ---
          ```
+         RULE_DESCRIPTION_HERE: the phrase placed here is like a "wake word" for the AI agent to use this agent. This is required of all cursor rules.
+         COMMA_SEPARATED_GLOBS_HERE: if a file is being edited that matches the given glob relative to the project root (.gitignore syntax), then this rule will be activated. This acts as a gate - globs are filled in, then the rule likely won't be activated unless it matches a glob. If the globs are not filled in, then it may be activated if the description sounds like a relevant tool to the current task to the AI agent.
       
-      2. **Use `mdc:` links** for file references, constructing a relative link from the PROJECT_ROOT to the file
+      2. **Use `mdc:` links** for file references, constructing a relative link from the PROJECT_ROOT to the file. The following is a link to a file at PROJECT_ROOT/src/folder/example.txt
          ```
-         [example.mdc](mdc:.cursor/rules/example.mdc)
+         [example.txt](mdc:src/folder/example.txt)
          ```
 
       3. **Use proper headers** (`#`, `##`, `###`) and avoid inconsistent formatting.
 
 examples:
   - input: |
       ---
-      description: "Example rule for formatting"
+      description: Example rule for formatting
+      globs: *.mdc
       ---
       # Sample Rule
       This rule enforces correct `.mdc` formatting.
+      (...)
     output: "Correctly formatted `.mdc` file"
 
 metadata:
diff --git a/journals/2025_03_02.md b/journals/2025_03_02.md
@@ -36,6 +36,13 @@
 			- [[Knowledge Gardening]]
 			- [[Package Management]]
 			- [[Stoic]]
+- ## #Typography
+	- [[Font/nerdfonts]] [Nerd Fonts - Iconic font aggregator, glyphs/icons collection, & fonts patcher](https://www.nerdfonts.com/)
 - ## #Unicode
-	- [[Font/unscii]]
-	- [[Unicode/Block/Symbols for Legacy Computing]]
+	- #Filed
+		- [[Font/unscii]]
+		- [[Semigraphics/Sextant Character]]
+		- [[Semigraphics/Sextant Characters/Py Grid Utility]]
+		- ### [[Unicode/Block/Symbols for Legacy Computing]]
+			- {{embed ((67c4c0b2-af03-4de6-ae00-405849fc19cd))}}
+		- [[Unicode/Block/Symbols for Legacy Computing/Ref]]
diff --git a/journals/2025_03_03.md b/journals/2025_03_03.md
@@ -0,0 +1,19 @@
+## [[AI Coding]]
+	- [[AI/Coding/Technique/Phased Planning/ai-coding dir]] #Updated
+		- Expanded the introductory section with a description of the files in the directory and some examples of various ticket folders
+		- Thinking that it might make sense to add these, but haven't recorded this anywhere else yet
+			- plan and checklist files for each stage in sub-folders to increase focus
+			- a file for CURRENT STAGE to store that state
+			- subfolders for issues from other repos
+	- [[CursorAI/Security/How To/Exclude Secrets from Indexing]]
+		- [[CursorAI/Forum/24/12/Questions on .gitignore, .cursorignore, .cursorban]]
+	- Expense of [[Claude 3.7 Sonnet]]
+		- [Is using claude-sonnet-3.7 more expensive than normal? : r/cursor](https://www.reddit.com/r/cursor/comments/1ixy6ip/is_using_claudesonnet37_more_expensive_than_normal/)
+			- Yes, it's fairly expensive. I'm using [[IDE/Cline]] extension in [[Windsurf]] and have spent $1.30 with 5 minutes. If you use it for a full day you could easily spend between 50 and 100 dollars.
+- #[[Tiling Window Manager]]
+	- [What’s the best window manager? : r/macapps](https://www.reddit.com/r/macapps/comments/1arq5a6/whats_the_best_window_manager/)
+		- 31 upvotes for [[MacOS/Tiling/App/Rectangle]], which is what I currently use, but it doesn't have all the features I want. I really could benefit from learning more of the keyshorts, though. Unbelievably, even though it has many features I don't use, it doesn't have the features I want. I'd really like to have more of a window manager like [[awesomeWM]] when I was in linux. I'd love to be able to snap and pin tiny applications to a small dedicated section of the screen. I think I can do that with [[BentoBox]].
+		- 30 upvotes [[Mac/Tiling/App/Swish]]
+			- {{embed ((67c57577-3534-41bf-a123-dc60b5d4f7d6))}}
+		- 3 upvotes for [[Mac/Tiling/App/BentoBox]]
+			- {{embed ((67c5750d-d643-4175-918f-fd25893710dc))}}
diff --git a/pages/AI___Coding___Technique___Phased Planning___ai-coding dir.md b/pages/AI___Coding___Technique___Phased Planning___ai-coding dir.md
@@ -1,11 +1,26 @@
 #  AI Coding technique - Using an `.ai-coding/TICKET/` dir for staging [[SDLC]] planning artifacts by SDLC Phase
 	- ## Summary of the `/.ai-coding/TICKET-feature-name/` directory
 	  id:: 67c180c4-95f6-4d0b-b787-60d11eed3ff9
-		- Named after the ticket and a brief description of the feature; preferably the name of this directory matches the end of the branch name; `TICKET` is an external project management ticket reference from [[JIRA]], [[GitHub/Issue]], [[Gitlab/Issue]], [[JetBrains/YouTrack]], etc, so something like `ASDF-123` for Jira
-		- Contains all planning and documentation assets for a single feature's implementation. Here they are, broken down by the **Phase** in which they are created or used.
+		- Named after the ticket and a brief description of the feature; preferably the name of this directory matches the end of the branch name; `TICKET` is an external project management ticket reference.
+			- ### Examples of `TICKET` references
+				- [[JIRA]] - `ASDF-123`
+				- [[GitHub/Issue]] - by convention, `gh-issue-123` for an issue in the current repo
+				- [[Gitlab/Issue]] - by convention, `gl-issue-123` for an issue in the current repo
+		- This directory contains all planning and documentation assets for a single feature's implementation. Here's an example full directory with all files for a github issue:
+			- `/.ai-coding/gl-issue-123-feature-name/`
+				- [[AI/Coding/v0/File/1-TICKET-original-issue.md]]
+				- [[AI/Coding/v0/File/1-TICKET-repomix.config.json]]
+				- [[AI/Coding/v0/File/2-TICKET-technical-specification.md]]
+				- [[AI/Coding/v0/File/3-TICKET-staged-implementation-plan.md]]
+				- [[AI/Coding/v0/File/6-TICKET-staged-implementation-checklist.md]]
+				- [[AI/Coding/v0/File/6-TICKET-qa-todo.md]]
+				- [[AI/Coding/v0/File/6-TICKET-qa-summary.md]]
+				- [[AI/Coding/v0/File/7-TICKET-mr-summary.md]]
+				- [[AI/Coding/v0/File/8-TICKET-mr-handoff.md]]
+	- ## Phases and their [[Intermediate Packets]] AKA output files
 		- ### [[AI/Coding/v0/Phase/0 - Preparation]]
 		  id:: 67c2d185-4821-4b6f-80f9-51b05cdb859e
-			- Before beginning work on a ticket, even before assembling materials to work on the ticket, it helps to have a the coding environment is correctly configured. This includes but is not limited to:
+			- Before beginning work it is a good idea to prepare the coding environment for AI coding. This includes but is not limited to:
 				- downloading the repository
 				- setting up the IDE
 					- ensuring that [[Prompts]] for [[AI Coding]] are configured and accessible
diff --git a/pages/Ableton___Packs___building-max-devices___02_M4L_Intro.md b/pages/Ableton___Packs___building-max-devices___02_M4L_Intro.md
@@ -5,7 +5,7 @@
 - ## DONE Page 2/9 - [[Ableton/Max for Live/MIDI Effect/Note Doubler]] in "Track 1 Max Patching"
   id:: 67960248-7168-46b2-af54-5ecfa125cfd6
   collapsed:: true
-	- so many [[Nerd Safari]]s await
+	- so many [[Nerd/Safari]]s await
 		- [[c74/max/Time Value Syntax]]
 		  collapsed:: true
 			- Here is a listing of the note and tick values associated with common note durations. Note value abbreviations that can be used in Max to specify time are in bold.
diff --git a/pages/CursorAI___Forum___24___12___Questions on .gitignore, .cursorignore, .cursorban.md b/pages/CursorAI___Forum___24___12___Questions on .gitignore, .cursorignore, .cursorban.md
@@ -0,0 +1,4 @@
+date-created:: [[2024/12]]
+
+- # [Questions on .gitignore, .cursorignore, .cursorban - Feedback - Cursor - Community Forum](https://forum.cursor.com/t/questions-on-gitignore-cursorignore-cursorban/34713)
+	-
diff --git a/pages/Font___nerdfonts.md b/pages/Font___nerdfonts.md
@@ -0,0 +1,4 @@
+alias:: [[nerdfonts]]
+
+- # [Nerd Fonts - Iconic font aggregator, glyphs/icons collection, & fonts patcher](https://www.nerdfonts.com/)
+	-
diff --git a/pages/Mac___Tiling___App___BentoBox.md b/pages/Mac___Tiling___App___BentoBox.md
@@ -0,0 +1,8 @@
+alias:: [[BentoBox]]
+
+- # [macOS Window Manager | BentoBox 🍱](https://bentoboxapp.com/)
+	- ## [[My Notes]]
+	  id:: 67c5750d-d643-4175-918f-fd25893710dc
+		- #Price - $9 right now, $20 once they are at v1.0
+		- #Cool - let's you pick your layouts to snap to
+			- https://assets.bentoboxapp.com/bentobox-demo.mp4
diff --git a/pages/Mac___Tiling___App___Swish.md b/pages/Mac___Tiling___App___Swish.md
@@ -0,0 +1,7 @@
+# [Swish for macOS](https://highlyopinionated.co/swish/)
+	- ## [[My Notes]]
+	  id:: 67c57577-3534-41bf-a123-dc60b5d4f7d6
+		- #Price $16
+		- Very based on [[Trackpad/Gestures]]
+	- Trailer
+		- https://highlyopinionated.co/swish/media/trailer.mp4
diff --git a/pages/Nerd___Safari.md b/pages/Nerd___Safari.md
@@ -0,0 +1 @@
+alias:: [[Nerd Safari]]
diff --git a/pages/Person___Devine Lu Linvega.md b/pages/Person___Devine Lu Linvega.md
@@ -10,4 +10,5 @@ alias:: [[Username/neauoire]]
 		- ![Divine and Rek](https://spaces.is/media/pages/loversmagazine/interviews/devine-lu-linvega/12eb16a9e9-1704123838/crossed-ocean.jpg)
 	- [[Person/Devine Lu Linvega/Garden/Lifestyle FAQs]]
 - [[Person/Devine Lu Linvega/GitHub]] - https://github.com/neauoire
-- Part of [[Org/Hundredrabbits]]
+- Part of [[Org/Hundredrabbits]]
+-
diff --git a/pages/Person___Viznut.md b/pages/Person___Viznut.md
@@ -5,7 +5,7 @@ tags:: [[Coder]]
 	- ## [[My Notes]]
 	  id:: 67c4b361-6c2f-409f-acbc-37f36ac86418
 		- creator of the beautiful [[Font/unscii]]
-		- culturally adjacent to [[Person/Divine lu Linvega]] and [[Perma/Computing]]; see also his essay [[Person/Viznut/Article/future]]
+		- culturally adjacent to [[Person/Devine Lu Linvega]] and [[Perma/Computing]]; see also his essay [[Person/Viznut/Article/future]]
 - ## Links
 	- ### [[Person/Viznut/Web]] http://viznut.fi/en/
 		- #### #Writing
diff --git a/pages/Person___Viznut___Article___future.md b/pages/Person___Viznut___Article___future.md
@@ -3,7 +3,7 @@ date-created:: [[2024/04]]
 
 - # [viznut:future](http://viznut.fi/en/future.html)
 	- ## [[My Notes]]
-		- reminds me of [[Person/Divine lu Linvega]] with the [[Perma/Computing]] aesthetic
+		- reminds me of [[Person/Devine Lu Linvega]] with the [[Perma/Computing]] aesthetic
 	- ## Summaries and Excerpts
 		- two types of futuristic images available for today's people
 			- "bright"
diff --git a/pages/Semigraphics___Sextant Character.md b/pages/Semigraphics___Sextant Character.md
@@ -0,0 +1,75 @@
+alias:: [[Semigraphics/Sextant Characters]]
+
+- # Sextant Character Grids from [[Unicode/Block/Symbols for Legacy Computing]]
+	- Using the characters from [Symbols for Legacy Computing - Wikipedia](https://en.wikipedia.org/wiki/Symbols_for_Legacy_Computing), we can render a 2x3 grid. These characters aren't on every platform. On the mac, Family name: `IBM 3270`, PostScript name: `3270-Regular` renders these.
+		- The following mappings assume that we're mapping a grid that's two cells wide (A, B) and three cells tall (1, 2, 3). As a convention, we'll annotate the grids by listing the cells that are alive in alphabetical order, grouped by the number of cells in the grid that are alive.
+	- There's a [[Semigraphics/Sextant Characters/Py Grid Utility]] which makes it easy to reference these using grid coordinates.
+	- ## Zero Cells
+		- Zero characters alive in six-grid: `🮓` (U+1FB93)
+	- ## One Character
+		- 1A: `🬀`
+		- 1B: `🬁`
+		- 2A: `🬃`
+		- 2B: `🬇`
+		- 3A: `🬏`
+		- 3B: `🬞`
+	- ## Two Characters
+		- 1A, 1B: `🬂`
+		- 1A, 2A: `🬄`
+		- 1A, 2B: `🬈`
+		- 1A, 3A: `🬐`
+		- 1A, 3B: `🬟`
+		- 1B, 2B: `🬉`
+		- 1B, 3A: `🬑`
+		- 1B, 3B: `🬠`
+		- 2A, 1B: `🬅`
+		- 2A, 2B: `🬋`
+		- 2A, 3A: `🬓`
+		- 2A, 3B: `🬢`
+		- 2B, 3A: `🬖`
+		- 2B, 3B: `🬦`
+		- 3A, 3B: `🬭`
+	- ## Three Characters
+		- 1A, 1B, 2A: `🬆`
+		- 1A, 1B, 2B: `🬊`
+		- 1A, 2A, 2B: `🬌`
+		- 1B, 2A, 2B: `🬍`
+		- 1A, 1B, 3A: `🬒`
+		- 1B, 2A, 3A: `🬔`
+		- 1A, 2B, 3A: `🬗`
+		- 1B, 2B, 3A: `🬘`
+		- 2A, 2B, 3A: `🬚`
+		- 1A, 1B, 3B: `🬡`
+		- 1A, 2A, 3B: `🬣`
+		- 1B, 2A, 3B: `🬤`
+		- 1A, 2B, 3B: `🬧`
+		- 2A, 2B, 3B: `🬩`
+		- 1A, 3A, 3B: `🬮`
+		- 1B, 3A, 3B: `🬯`
+		- 2A, 3A, 3B: `🬱`
+		- 2B, 3A, 3B: `🬵`
+	- ## Four Characters
+		- 1A, 1B, 2A, 2B: `🬎`
+		- 1A, 2A, 1B, 2B: `🬕`
+		- 1A, 1B, 2B, 3A: `🬙`
+		- 1A, 2A, 2B, 3A: `🬛`
+		- 1B, 2A, 2B, 3A: `🬜`
+		- 1A, 1B, 2A, 3B: `🬥`
+		- 1A, 1B, 2B, 3B: `🬨`
+		- 1A, 2A, 2B, 3B: `🬪`
+		- 1B, 2A, 2B, 3B: `🬫`
+		- 1A, 1B, 3A, 3B: `🬰`
+		- 1A, 2A, 3A, 3B: `🬲`
+		- 1B, 2A, 3A, 3B: `🬳`
+		- 1A, 2B, 3A, 3B: `🬶`
+		- 1B, 2B, 3A, 3B: `🬷`
+		- 2A, 2B, 3A, 3B: `🬹`
+	- ## Five Characters
+		- 1A, 1B, 2A, 2B, 3A: `🬝`
+		- 1A, 1B, 2A, 2B, 3B: `🬬`
+		- 1A, 1B, 2A, 3A, 3B: `🬴`
+		- 1A, 2B, 2B, 3A, 3B: `🬸`
+		- 1A, 2A, 2B, 3A, 3B: `🬺`
+		- 1B, 2A, 2B, 3A, 3B: `🬻`
+	- ## All Six Characters
+		- `🮋`
diff --git a/pages/Semigraphics___Sextant Characters___Py Grid Utility.md b/pages/Semigraphics___Sextant Characters___Py Grid Utility.md
diff --git a/pages/Trackpad___Gesture.md b/pages/Trackpad___Gesture.md
diff --git a/pages/Unicode___Block___Symbols for Legacy Computing.md b/pages/Unicode___Block___Symbols for Legacy Computing.md
diff --git a/pages/Unicode___Block___Symbols for Legacy Computing___Ref.md b/pages/Unicode___Block___Symbols for Legacy Computing___Ref.md
diff --git a/pages/Window___Manager___Tiling.md b/pages/Window___Manager___Tiling.md
diff --git a/pages/awesomeWM.md b/pages/awesomeWM.md

-Original file line number
+Diff line change
@@ @@ -0,0 +1,4 @@ @@
 +date-created:: [[2024/12]]
++
 +- # [Questions on .gitignore, .cursorignore, .cursorban - Feedback - Cursor - Community Forum](https://forum.cursor.com/t/questions-on-gitignore-cursorignore-cursorban/34713)
 +	-