update rules

Author: semio

automation-api/.rules

@@ -2,7 +2,7 @@
  - 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 overview, the plan, the todo list.
+   1. the overview, the plan, the todo list. (no need to put development setup details)
    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)
  - breaking changes are fine, we don't need to keep backward compatibility.
@@ -23,8 +23,8 @@
 # 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`
+   - Hooks will run automatically on git commit. (So you don't need to run it manually)
+   - 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