القائمة
Use when working with poorly typed or legacy Python code. Covers gradual typing, safe annotation strategies, dynamic attributes, and monkeypatching without breaking behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | python-legacy |
| description | Use when working with poorly typed or legacy Python code. Covers gradual typing, safe annotation strategies, dynamic attributes, and monkeypatching without breaking behavior. |
Any with a # TODO(type): <reason> marker — do not guessProtocol over concrete types for duck-typed interfacestyping.cast only when you know the runtime type but the static checker disagreesfrom __future__ import annotations before introducing annotations in legacy modules__getattr__ / setattr / getattr patterns, prefer TypedDict or dataclass if possibleobject and narrow with isinstance at use sitespytest-mock (mocker.patch) or unittest.mock.patchmocker.spy() over mocker.patch() when you only need assertionsDetect the manager by lockfile, not by guessing:
uv.lock → uvpoetry.lock → poetryrequirements.txt → warn the user and suggest migrating to uvpip install / uv pip install must NEVER be used to add dependencies to a project.
They manage a bare environment without updating pyproject.toml, so the dependency
is invisible to the lockfile and will be lost on the next uv sync.
Correct commands (verified against uv add --help and poetry add --help):
| Action | uv | poetry |
|---|---|---|
| Add runtime dep | uv add <pkg> | poetry add <pkg> |
| Add dev dep | uv add --dev <pkg> | poetry add --group dev <pkg> |
| Add to a named group | uv add --group <g> <pkg> | poetry add --group <g> <pkg> |
| Add optional/extra dep | uv add --optional <e> <p> | poetry add <pkg> (edit toml) |
| Remove a dep | uv remove <pkg> | poetry remove <pkg> |
| Sync env from lockfile | uv sync | poetry sync / poetry install |
uv pip <subcommand> is a low-level pip-compatible interface for environments
WITHOUT project metadata. Do not reach for it in normal project work.
Run the type checker after each batch of annotations: basedpyright.
assert isinstance(result, expected_type) in tests as runtime type guards# TODO(type): <what and why> — unknown or complex type# LEGACY: <explanation> — explaining a weird pattern that should not be replicated# REFACTOR: <idea> — safe improvement to do laterUse when migrating a Python project from Poetry to uv. Covers running `uvx migrate-to-uv`, fixing pyproject.toml conversion gaps, rewriting Dockerfiles (poetry install -> uv sync), updating .gitlab-ci.yml, and verifying the result. Trigger keywords: migrate poetry to uv, migrate-to-uv, poetry -> uv, switch to uv, replace poetry.
Use when committing, creating PRs, or managing git history. Conventional commits, pre-commit hooks with ruff and basedpyright, branching conventions.
Use when first opening an unfamiliar Python project. Quick analysis of project structure, dependencies, entry points, test setup, and tooling.
Use when refactoring Python code safely. Covers extract method/class/module, dependency inversion, constants extraction, and test-protected changes.
Use when writing or editing Python code. Enforces strict typing with basedpyright, ruff linting and formatting, modern Python 3.12+ idioms.
Use when writing tests for Python code. Covers pytest conventions, fixtures, mocking, strict type-checked tests.