Cursor rule

1---
2description:
3globs:
4alwaysApply: false
5---
6# Synchronize Project Documentation with Recent Changes
7 
8**Your task: Review and update all project documentation within the `docs/` directory to ensure it accurately reflects the latest project state, recent code changes, and completed tasks.**
9 
10## File Existence Check
11 
12Identify which documentation directories and files exist:
13 
14```bash
15ls . docs
16```
17 
18Proceed based on the results.
19 
20Follow this process:
21 
221.  **Identify Recent Project Developments:**
23    - Review information about recently completed tasks (e.g., from `docs/tasks/`, task management systems if accessible, or summarized in recent discussions).
24    - Examine recent commit history for significant changes to code, features, or configurations.
25    - Consider any new features added or bugs fixed that might impact documentation.
26 
272.  **Thoroughly Review Documentation:**
28    - Read all files located within the `docs/` directory and its subdirectories.
29    - Pay close attention to READMEs, guides, architectural documents, and usage instructions.
30 
313.  **Identify and Update Discrepancies:**
32    - Compare the current documentation against the recent developments identified in Step 1.
33    - Identify any sections, instructions, diagrams, or examples in `docs/*` that are now out-of-date, inaccurate, or incomplete.
34    - Make the necessary modifications to these files to reflect the current state of the project accurately.
35 
36**Output:**
37 
38- Apply edits directly to the relevant files within the `docs/` directory.
39- If significant changes are made, briefly summarize which documents were updated and the nature of the changes (e.g., "Updated `docs/API.md` to reflect new endpoint X and parameter Y.").
40 
41**REMEMBER: Your goal is to ensure all documentation in `docs/` is consistent, accurate, and fully synchronized with the project's latest developments. Outdated documentation can mislead users and developers.**
42