Cursor rule

1---
2description: 
3globs: 
4alwaysApply: true
5---
6You are working on *Vrooli*, an innovative web application that orchestrates AI agents for complex tasks. Follow these guidelines to ensure cohesive execution and continuous process improvement.
7 
81. Project Orientation
9- **Documentation Check:**  
10  - [README.md](mdc:README.md) Understand the project vision, roadmap, and overall requirements.  
11  - [README.md](mdc:docs/architecture/README.md) and [TASKS.md](mdc:TASKS.md): Review project structure and task planning guidelines.
12- **Planning & Learning:**  
13  - Draft a brief plan before coding and await confirmation.
14  - After plan confirmation, store the active plan in a markdown file in the `/scratch` folder for future reference. 
15  - As you work on the task, you are encouraged to store other things in the `/scratch` folder like things you'd attempted and how they worked out, discoveries on how certain parts of the code work, etc.
16- **Development Standards:**  
17  - Use ESM TypeScript for all code.
18  - Include comprehensive docstrings and clear comments on complex logic.
19  - Write unit tests using Mocha, Chai, and Sinon.
20  - Use relative imports with the `.js` extension, but remember when searching for files to use the typed counterpart (`.ts` or `.tsx`).
21- **Dependencies:**  
22  - **Never** install new packages without explicit permission!
23   
242. Dynamic Task Management with Documentation Update
25- **A. Task Identification and Clarification**
26  - Analyze each new task description to classify it (debugging, UI component creation, refactoring, etc.) and ask clarifying questions if needed.
27- **B. Documentation Consultation & Integration**
28  - Search the `/docs` directory for an appropriate process guide based on the task type.
29  - If no guide exists, confirm whether to use default practices and consider creating one.
30- **C. Execution & Updates**
31  - Use file operations (read/write, search, grep) to retrieve and update process guides.
32  - If deviations from current guidelines occur, ask:  
33    "I've noted differences from our documented process. Update `/docs/<relevant-guide>.md`?"
34 
353. Feedback and Continuous Improvement
36- **Monitor Communication:**  
37  - Detect signs of frustration or terse commands. When detected, prompt:  
38    "It seems we might need to refine our process—shall we adjust the guidelines?"
39- **Session Retrospective:**  
40  - After completing a task, ask:  
41    "Do you have any suggestions or improvements for our process?"
42  - Record actionable feedback to update [agent.mdc](mdc:.cursor/rules/agent.mdc) (this prompt) and/or documentation promptly.
43 
444. Autonomous Task Commands
45- **Task Command Reference:**
46  - All task commands and their detailed descriptions are defined in [TASKS.md](mdc:TASKS.md).
47  - Follow the command patterns defined in that file when executing any task operation
48  - Any updates to command behavior should be made directly in [TASKS.md](mdc:TASKS.md) as the single source of truth
49  - Commands in this context are not scripts to be executed - they are processes to follow
50 
51 
52