.cursorrules (deprecated)

1# Cursor Rules
2 
3## ⚠️ MANDATORY PRE-IMPLEMENTATION CHECKLIST ⚠️
4STOP! Before writing ANY code or suggesting ANY changes:
5 
61. 🔍 SEARCH FIRST:
7```bash
8   # REQUIRED: Run these searches and document results
9   grep_search for functionality
10   file_search for similar files
11   list_dir in relevant directories
12```
13 
142. 📝 DOCUMENT FINDINGS:
15```markdown
16   # REQUIRED: Fill this out
17   ## Existing Files Found:
18   - [List all relevant files found with full paths]
19   - [Include file sizes and last modified dates if relevant]
20   
21   ## Existing Functionality:
22   - [Describe what already exists in detail]
23   - [Note any patterns or architectural approaches used]
24   
25   ## Gaps Identified:
26   - [List what's missing or needs enhancement]
27   - [Identify technical debt or issues in existing code]
28   
29   ## Implementation Decision Tree:
30   - Is there existing code that serves this purpose? [Yes/No]
31   - Can existing code be enhanced to meet requirements? [Yes/No]
32   - Is creating new code justified? [Yes/No, with reasoning]
33   
34   ## Proposed Approach:
35   - [ ] Enhance existing code at [file path]
36   - [ ] Create new files (requires detailed justification)
37   - [ ] Refactor existing code at [file path]
38   
39   ## Implementation Plan:
40   1. [First step with estimated effort]
41   2. [Second step with estimated effort]
42   3. [Additional steps as needed]
43```
44 
453. ✋ WAIT FOR APPROVAL:
46   - Present findings to user with clear options
47   - Get explicit approval for chosen approach
48   - Never proceed with new files if similar functionality exists
49   - Document approval in the implementation plan
50 
51❌ IF YOU SKIP THIS CHECKLIST, YOU ARE VIOLATING THE MOST IMPORTANT RULE ❌
52