Update .rules

Author: semio

automation-api/.rules

@@ -1,14 +1,31 @@
  # General Rules for Automation API
-
- - when start a task, try to find if there are related items in backlogs. Read them to know the current status about the project.
- - if no related items found. Plan your action and create the plan in backlogs/
+ - before start a task, try to find if there are related items in backlogs. Read them to know the current status about the project.
+ - if no related items found, plan your action and create the plan in backlogs/. Read the README.md file in the project folder.
  - An item in backlogs/ should have 2 sections:
-   1. the plan
-   2. summarization of each edit session about what has been done.
+   1. the overview, the plan, the todo list.
+   2. summarization of what has been done.
  - after a task is done, update the backlog and README.md/DEV.md in the project folder. (automation_api/README.md / automation_api/DEV.md)
- - at current stage, don't keep backward compatibility, breaking changes are fine.
+ - breaking changes are fine, we don't need to keep backward compatibility.
 
 # How to test the gm-eval command
-- Remind me (the human user) about I should update the configuration speadsheet before start.
 - create a temp folder in project root
-- in the temp folder, run `gm-eval download` and then `gm-eval run`
+- in the temp folder, run the gm-eval commands as you need
+- double check the downloaded ai_eval_sheets. If they contains many data (more than 5 questions and 5 prompts), stop and confirm if you can continue first.
+
+# Environment
+- Use Python version specified in .python-version
+- Always work within the virtual environment
+- use uv for virtual environment
+- use poethepoet for tasks
+- use pytest for tests
+- Keep pyproject.toml updated when adding new dependencies
+
+# Code Quality
+- We use pre-commit hooks for code quality checks
+   - Run `pre-commit install` to set up the hooks (only needed for new env)
+   - Hooks will run automatically on git commit
+   - You can also run manually with `pre-commit run --all-files`
+- use snake_case for variable names
+- use all uppercase for constants
+- prefer functional programming style
+- write meaningful comments, avoid comments that are redundant or unnecessary or just "user told me to do it"