菜单
Add or manage third-party dependencies in a Polylith workspace. Use when the user wants to install a new library (e.g., requests, fastapi) for a brick or project.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/DavidVujic/python-polylith --skill polylith-dependency-management命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
[Internal sub-skill of `polylith-migrate-orchestrator`. Do not load directly — load `polylith-migrate-orchestrator` first, which drives all phases.] Analyze the project's import graph to find how the original namespace is referenced, choose the namespace-rewrite strategy (shim vs shimless), detect circular imports, and list symbols exported by the original namespace.
[Internal sub-skill of `polylith-migrate-orchestrator`. Do not load directly — load `polylith-migrate-orchestrator` first, which drives all phases.] Update imports in the new base location to reference the new namespace instead of the original namespace.
[Internal sub-skill of `polylith-migrate-orchestrator` (optional, runs only when opted in during `polylith-migrate-discover`). Do not load directly — load `polylith-migrate-orchestrator` first.] Align the project's linter and formatter with the **workspace's** configured tool (whatever it is — ruff, black+isort+flake8, pylint, etc.). Removes project-specific config and consolidates rules into the workspace root.
| name | polylith-dependency-management |
| description | Add or manage third-party dependencies in a Polylith workspace. Use when the user wants to install a new library (e.g., requests, fastapi) for a brick or project. |
💡 Terminology: this skill uses Polylith terms like brick, project, and development project. If they're unfamiliar, load
polylith-conceptsfirst.
Polylith manages third-party dependencies differently than standard Python projects.
pyproject.toml (the development project). This ensures local REPLs, tests, and the shared lockfile work correctly. Use your package manager (e.g., uv add <package>, poetry add <package>) at the workspace root.projects/<name>):
If a library is required for production by a specific deployable project, it must also be added to that project's pyproject.toml under projects/<name>/. Do this by manually editing the dependencies array in projects/<name>/pyproject.toml.⚠ Never add dependencies to a brick's directory. Bricks do not have their own
pyproject.tomlfiles.
requests to an api projectInstall it at the root so the lockfile updates and it's available for local development:
uv add requests
Manually add it to the deployable project that needs it:
Edit projects/api/pyproject.toml.
Important Versioning Rule: Before adding the dependency to the project, check the root pyproject.toml. If it contains a [tool.uv.workspace] section (e.g., members = ["projects/*"]), then uv workspaces is enabled.
If uv workspaces is enabled, do not specify the version in the project's pyproject.toml. Just use the package name, because versions are centrally pinned in the root. If workspaces are not enabled, then you should specify the version.
# WITH uv/poetry workspaces enabled (Recommended):
dependencies = [
"requests"
]
# WITHOUT workspaces enabled:
dependencies = [
"requests>=2.31.0"
]
Run poly check (load polylith-check) to verify the workspace is valid. poly check will catch if a project imports requests but forgot to declare it in its pyproject.toml.
poly libs (load polylith-libs) to inspect current dependency usage across projects.