From 17555a490787e5b0c51421b91a9106af5eb8c231 Mon Sep 17 00:00:00 2001 From: Oleksandr Bezdieniezhnykh Date: Mon, 6 Apr 2026 04:59:44 +0300 Subject: [PATCH] Update coding rules to enforce source code organization and clarify Python project structure --- .cursor/rules/coderule.mdc | 1 + .cursor/rules/python.mdc | 1 - 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/.cursor/rules/coderule.mdc b/.cursor/rules/coderule.mdc index af70783..a90389d 100644 --- a/.cursor/rules/coderule.mdc +++ b/.cursor/rules/coderule.mdc @@ -21,3 +21,4 @@ alwaysApply: true - Make sure we don't commit binaries, create and keep .gitignore up to date and delete binaries after you are done with the task - Never force-push to main or dev branches +- Place all source code under the `src/` directory; keep project-level config, tests, and tooling at the repo root diff --git a/.cursor/rules/python.mdc b/.cursor/rules/python.mdc index fc8e934..95d0628 100644 --- a/.cursor/rules/python.mdc +++ b/.cursor/rules/python.mdc @@ -8,7 +8,6 @@ globs: ["**/*.py", "**/pyproject.toml", "**/requirements*.txt"] - Use type hints on all function signatures; validate with `mypy` or `pyright` - Use `pydantic` for data validation and serialization - Import order: stdlib -> third-party -> local; use absolute imports -- Use `src/` layout to separate app code from project files - Use context managers (`with`) for resource management - Catch specific exceptions, never bare `except:`; use custom exception classes - Use `async`/`await` with `asyncio` for I/O-bound concurrency