Cursor rule

1---
2description:
3globs:
4alwaysApply: false
5---
6# Synchronize Project Documentation with Recent Changes
7 
8 
9**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.**
10 
11## File Existence Check
12 
13Identify which documentation directories and files exist:
14 
15```bash
16ls . docs
17```
18 
19Proceed based on the results.
20 
21Follow this process:
22 
231.  **Identify Recent Project Developments:**
24    - Review information about recently completed tasks by querying closed GitHub issues (e.g., `gh issue list --state closed --label task`).
25    - Examine recent commit history for significant changes to code, features, or configurations.
26    - Consider any new features added or bugs fixed that might impact documentation.
27 
282.  **Thoroughly Review Documentation:**
29    - Read all files located within the `docs/` directory and its subdirectories.
30    - Pay close attention to READMEs, guides, architectural documents, and usage instructions.
31 
323.  **Identify and Update Discrepancies:**
33    - Compare the current documentation against the recent developments identified in Step 1.
34    - Identify any sections, instructions, diagrams, or examples in `docs/*` that are now out-of-date, inaccurate, or incomplete.
35    - Make the necessary modifications to these files to reflect the current state of the project accurately.
36 
37**Output:**
38 
39- Apply edits directly to the relevant files within the `docs/` directory.
40- 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.").
41 
42**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.**
43