Update Cursor rules to combine VAN's old rules with Ghuntley's https://ghuntley.com/stdlib/

Author: ezrover

.cursor/rules/1stRule.mdc

@@ -0,0 +1,75 @@
+---
+description: 1stRule Cursor Rules Location
+globs: *.mdc
+---
+# Cursor Rules Location
+
+Rules for placing and organizing Cursor rule files in the repository.
+
+<rule>
+name: cursor_rules_location
+description: Standards for placing Cursor rule files in the correct directory
+filters:
+  # Match any .mdc files
+  - type: file_extension
+    pattern: "\\.mdc$"
+  # Match files that look like Cursor rules
+  - type: content
+    pattern: "(?s)<rule>.*?</rule>"
+  # Match file creation events
+  - type: event
+    pattern: "file_create"
+
+actions:
+  - type: reject
+    conditions:
+      - pattern: "^(?!\\.\\/\\.cursor\\/rules\\/.*\\.mdc$)"
+        message: "Cursor rule files (.mdc) must be placed in the .cursor/rules directory"
+
+  - type: suggest
+    message: |
+      When creating Cursor rules:
+
+      1. Always camelCased place rule files in PROJECT_ROOT/.cursor/rules/:
+         ```
+         .cursor/rules/
+         ├── yourRuleName.mdc
+         ├── anotherRule.mdc
+         └── ...
+         ```
+
+      2. Follow the naming convention:
+         - Use kebab-case for filenames
+         - Always use .mdc extension
+         - Make names descriptive of the rule's purpose
+
+      3. Directory structure:
+         ```
+         PROJECT_ROOT/
+         ├── .cursor/
+         │   └── rules/
+         │       ├── yourRuleName.mdc
+         │       └── ...
+         └── ...
+         ```
+
+      4. Never place rule files:
+         - In the project root
+         - In subdirectories outside .cursor/rules
+         - In any other location
+
+examples:
+  - input: |
+      # Bad: Rule file in wrong location
+      rules/myRule.mdc
+      myRule.mdc
+      .rules/myRule.mdc
+
+      # Good: Rule file in correct location
+      .cursor/rules/myRule.mdc
+    output: "Correctly placed Cursor rule file"
+
+metadata:
+  priority: high
+  version: 1.0
+</rule>

.cursor/rules/main.mdc renamed to .cursor/rules/2ndRule.mdc

@@ -87,14 +87,14 @@ Match process complexity to task requirements:
 
 | Critical Process | Reference Link | When to Consult |
 |------------------|----------------|-----------------|
-| Adaptive Workflow | [workflow.mdc](mdc:.cursor/rules/Core%20Implementation/workflow.mdc) | Start of any task |
-| Task Tracking | [task-tracking.mdc](mdc:.cursor/rules/Core%20Implementation/task-tracking.mdc) | When updating task status |
-| Memory Structure | [memory-bank.mdc](mdc:.cursor/rules/Core%20Implementation/memory-bank.mdc) | Before updating docs |
-| Command Safety | [command-execution.mdc](mdc:.cursor/rules/Core%20Implementation/command-execution.mdc) | Before running commands |
-| VAN Protocol | [van-protocol.mdc](mdc:.cursor/rules/Core%20Implementation/van-protocol.mdc) | When processing VAN command |
-| Complex Tasks | [verification-checklist.mdc](mdc:.cursor/rules/Core%20Implementation/verification-checklist.mdc) | For Level 3-4 tasks |
-| Creative Phases | [creative-phase-guidelines.mdc](mdc:.cursor/rules/Core%20Implementation/creative-phase-guidelines.mdc) | For creative work |
-| Creative Triggers | [creative-phase-triggers.mdc](mdc:.cursor/rules/Core%20Implementation/creative-phase-triggers.mdc) | When to enter creative phases |
+| Adaptive Workflow | [workflowRule.mdc](mdc:.cursor/rules/Core%20Implementation/workflowRule.mdc) | Start of any task |
+| Task Tracking | [taskTrackingRule.mdc](mdc:.cursor/rules/Core%20Implementation/taskTrackingRule.mdc) | When updating task status |
+| Memory Structure | [memoryBankRule.mdc](mdc:.cursor/rules/Core%20Implementation/memoryBankRule.mdc) | Before updating docs |
+| Command Safety | [commandExecutionRule.mdc](mdc:.cursor/rules/Core%20Implementation/commandExecutionRule.mdc) | Before running commands |
+| Vibe Protocol | [aSingleTopRule.mdc](mdc:.cursor/rules/Core%20Implementation/aSingleTopRule.mdc) | When processing Vibe command |
+| Complex Tasks | [verificationChecklistRule.mdc](mdc:.cursor/rules/Core%20Implementation/verificationChecklistRule.mdc) | For Level 3-4 tasks |
+| Creative Phases | [creativePhaseGuidelinesRule.mdc](mdc:.cursor/rules/Core%20Implementation/creativePhaseGuidelinesRule.mdc) | For creative work |
+| Creative Triggers | [creativePhaseTriggersRule.mdc](mdc:.cursor/rules/Core%20Implementation/creativePhaseTriggersRule.mdc) | When to enter creative phases |
 
 ## 📝 LEVEL 1: QUICK BUG FIX WORKFLOW
 

.cursor/rules/Extended Details/archive-examples.mdc renamed to .cursor/rules/Extended Details/archiveExamples.mdc

@@ -24,7 +24,7 @@ Objective: Create secure login functionality with JWT token support
 
 ## Section Header Tracking
 [ ] INITIALIZATION
-[ ] DOCUMENTATION SETUP 
+[ ] DOCUMENTATION SETUP
 [ ] TASK PLANNING
 [ ] IMPLEMENTATION
 [ ] REFLECTION
@@ -194,7 +194,7 @@ Now I'll implement the User model with validation and password hashing.
 
 ## Section Header Tracking
 [X] INITIALIZATION
-[X] DOCUMENTATION SETUP 
+[X] DOCUMENTATION SETUP
 [X] TASK PLANNING
 [X] IMPLEMENTATION
 [ ] REFLECTION

.cursor/rules/Extended Details/command-examples.mdc renamed to .cursor/rules/Extended Details/commandExamples.mdc

@@ -9,7 +9,7 @@ alwaysApply: false
 
 When creating any Memory Bank file, use these templates as the starting point. These are the ESSENTIAL templates that must be used for core files.
 
-⚠️ REFERENCE REQUIRED: For extended and specialized templates, I MUST read templates-extended.mdc.
+⚠️ REFERENCE REQUIRED: For extended and specialized templates, I MUST read templatesExtended.mdc.
 
 ## projectbrief.md Template
 ```markdown

.cursor/rules/Extended Details/creative-phase-examples.mdc renamed to .cursor/rules/Extended Details/creativePhaseExamples.mdc

@@ -1,18 +1,18 @@
 ---
-description: Adaptive VAN protocol implementation
+description: Adaptive Vibe Coding protocol implementation
 globs: 
 alwaysApply: true
 ---
-# ADAPTIVE VAN PROTOCOL
+# ADAPTIVE VIBE PROTOCOL
 
-> **TL;DR:** When user types "VAN", respond with "OK VAN", determine task complexity level, and adapt the workflow process accordingly. The system scales from quick bug fixes to complex system implementations.
+> **TL;DR:** When user types "Vibe", respond with "OK VAN", determine task complexity level, and adapt the workflow process accordingly. The system scales from quick bug fixes to complex system implementations.
 
 ## 🚀 QUICK START RESPONSE
 
-When the user types ONLY "VAN", immediately respond:
+When the user types ONLY "Vibe", immediately respond:
 
 ```
-OK VAN
+OK Lets Vibe...
 
 I'll determine the appropriate process level based on the task complexity:
 
@@ -61,7 +61,7 @@ Analyze the task to determine the appropriate complexity level:
 
 Check for critical files and create them if missing:
 
-1. Ensure `.cursorrules` exists (as a file, not directory)
+1. Ensure `.cursor` directory exists
 2. Ensure `memory-bank` directory exists
 3. Ensure `docs/archive` directory exists
 4. Ensure all core Memory Bank files exist, including tasks.md
@@ -178,7 +178,7 @@ I'll begin with a comprehensive review of all Memory Bank files...
 
 ## 🔄 WITH TASK INCLUDED
 
-When user includes a task with VAN:
+When user includes a task with VIBE:
 ```
 VAN
 I need to implement a login system
@@ -193,7 +193,7 @@ I need to implement a login system
 ## 📝 MEMORY BANK FILES
 
 The core Memory Bank files (ALL REQUIRED):
-- projectbrief.md
+- projectBrief.md
 - productContext.md
 - systemPatterns.md
 - techContext.md
@@ -203,7 +203,7 @@ The core Memory Bank files (ALL REQUIRED):
 
 ## ✓ VAN CHECKPOINT
 
-Before proceeding after VAN:
+Before proceeding after VIBE:
 - Have I verified all critical files exist?
 - Have I determined the appropriate complexity level?
 - Have I created tasks.md if it doesn't exist?
@@ -275,7 +275,7 @@ The complexity of creative phase documentation should match the task complexity
 - **Level 2 (Enhancement)**: Basic creative phase markers with summary
 - **Level 3-4 (Feature/System)**: Full creative phase structure with checkpoints
 
-See [creative-phase-examples.mdc](mdc:.cursor/rules/Extended%20Details/creative-phase-examples.mdc) for detailed examples.
+See [creativePhaseExamples.mdc](mdc:.cursor/rules/Extended%20Details/creativePhaseExamples.mdc) for detailed examples.
 
 ## 📋 LEVEL ESCALATION