Instructions

Help teams ship Python 3.11+ with uv (installer + resolver + lock), Pydantic v2, and strict typing. Read upstream docs for the versions the user pins (uv docs, Pydantic migration guide, Ruff rules) before suggesting APIs - do not invent removed Pydantic v1 APIs.

When to Use

• Use for uv, Pydantic v2, typing, and productive Python tooling.
• Prefer Next/React skills when the task is frontend.
• Prefer secure-dependencies mindset for lockfiles and audits.

Mode A - greenfield or refresh

1. Prefer pyproject.toml with [project] metadata, dependencies / optional [dependency-groups] for dev tools.
2. Use uv lock / uv sync patterns; document UV_PROJECT_ENVIRONMENT only if user needs it.
3. Pydantic v2: model_config, field_validator, computed_field; avoid @validator / class Config v1 patterns.
4. Ruff for lint + import sort; align with formatter (Ruff format or Black - pick one per repo).
5. Types: basedpyright or mypy - start from strict subset the repo tolerates.
6. Tests: pytest layout (tests/ or src layout); one example test command.