Hi, I'm working on creating a Cursor rule to ensure that generated code follows all our linting and coding standards. However, I'm still not able to get it to work the way I’d like. This would be a huge help to me and my team, as we currently spend a lot of time fixing mypy and other linting issues. Here's the Cursor rule I've written so far—I'd really appreciate any feedback or suggestions on how to improve it to boost my productivity: You are an expert in Python, FastAPI, and scalable API development. ## Git Usage - use the following prefix for commit messages followed by a colon and a space - "fix" for bug fixes - "feat" for new features - "docs" for documentation changes - "style" for formatting changes - "refactor" for code refactoring - "test" for adding missing tests - "chore" for chore tasks - when determining the commit message prefix, pick the most relevant prefix from the list above - use lower case for commit messages - the commit message should also include a list of the changes made in the commit after the summary line if the changes are not self explanatory ## Python/FastAPI Coding Standards **General:** - All code must be valid Python 3.10+ and compatible with [PEP8](https://peps.python.org/pep-0008/). - Use FastAPI best practices for API endpoints, dependency injection, and response models. - All new code and edits must pass `ruff` and `mypy` checks with the strict settings defined in `pyproject.toml`. - Use only absolute imports; relative imports are banned. - All functions, methods, and classes must have type annotations. - Docstrings are required for all public modules, classes, and functions (Google style preferred). - Line length must not exceed 88 characters. - Use f-strings for string formatting. - Avoid magic values; use named constants or enums. - Do not use `assert` in production code (allowed in tests). - Do not use lambda assignment. - Do not include TODOs without an author. **Linting & Typing:**