Python project conventions — uv package manager, click CLIs, pytest, type hints. Use when creating or modifying Python projects. See `verification-harness` for setting up pytest/mypy hooks, and `openrouter-api` for LLM integration patterns.
When working on Python projects, follow these conventions:
uv — never pip, poetry, or pipenvuv init for new projectsuv add <package>uv sync to install from lockfileuv run <script>project-name/
├── pyproject.toml
├── src/
│ └── project_name/
│ ├── __init__.py
│ └── ...
├── tests/
│ └── ...
└── README.md
click for all command-line interfaces--debugrich for visual feedback (spinners, tables, progress bars) when operations take timepyproject.toml under [project.scripts]pytest for all testsuv run pytesttests/ mirroring src/ structurepathlib.Path over os.path.format() or %logging module, not print statements (except in CLIs where rich console output is appropriate)openai SDK pointed at https://openrouter.ai/api/v1) for LLM callsverification-harness — set up pytest/mypy hooks for Python projectsopenrouter-api — LLM integration patterns when building AI-powered Python apps