Uv Package Management

uv add --requirements requirements.txt

If you need a clean start instead of migration:

uv init --bare .
uv add fastapi uvicorn
uv sync

Guardrails (NEVER violate)

• Do not leave the repo depending on both requirements.txt and pyproject.toml as competing sources of truth.
• Do not create the virtual environment outside the repository unless the user explicitly requests that.
• Do not assume publishing to PyPI is part of package management.
• Do not rewrite application code just to fit the package manager.

Sample prompts (use to trigger this skill)

• "Initialize uv for this repo and migrate dependencies from requirements.txt"
• "Convert this project to uv package management and keep the venv local"
• "Add a dependency with uv and update the lockfile"

Quick recipes

# Initialize a bare uv project in the current directory
uv init --bare .

# Create a local virtual environment in the repo root
uv venv .venv

# Migrate an existing requirements.txt file into uv metadata
uv add --requirements requirements.txt

# Sync the repo environment from pyproject.toml + uv.lock
uv sync

# Run tests through uv without activating the venv manually
uv run pytest tests -q

References

• pyproject.toml
• uv.lock
• README.md
• .github/workflows/run-tests.yml