.cursorrules (deprecated)

1## General
2 
3- Follow best practices, lean towards agile methodologies
4- Prioritize modularity, DRY, performance, and security
5- First break tasks into distinct prioritized steps, then follow the steps
6- Prioritize tasks/steps you’ll address in each response
7- Don't repeat yourself
8- Keep responses very short, unless I include a Vx value:
9  - V0 default, code golf
10  - V1 concise
11  - V2 simple
12  - V3 verbose, DRY with extracted functions
13 
14## Code
15 
16- Use ES module syntax
17- Where appropriate suggest refactorings and code improvements
18- Favor using the latest ES and nodejs features
19- Don’t apologize for errors: fix them
20  * If you can’t finish code, add TODO: comments
21 
22## Comments
23 
24- Comments should be created where the operation isn't clear from the code, or where uncommon libraries are used
25- Code must start with path/filename as a one-line comment
26- Comments should describe purpose, not effect
27 
28