Python with uv

Use the repository's existing Python and verification choices first; use uv for dependency and execution operations unless a documented repository command wraps them.

Choose the Mode

• Project: a pyproject.toml, lockfile, shared package, or local imports define an environment.
• Standalone script: one file or stdin should run without creating a project.
• Use --no-project only when the invocation must ignore the surrounding project and does not import its code.

Project Workflow

1. Inspect pyproject.toml, lockfiles, repository instructions, and existing tools.
2. Initialize only genuinely new projects with uv init. Add or remove dependencies with uv add and uv remove; use uv sync to reconcile declared state.
3. Run Python and project tools through uv run or the repository's documented wrapper.
4. Preserve the established test, lint, type-check, coverage, and hook stack. For a new project with no stated requirements, add only tools that serve the requested quality bar.
5. Update and inspect the lockfile when dependency inputs change.
6. Run the narrow checks needed during iteration, then the repository's aggregate gate.