菜单
A development process for Python applications that uses TDD to iterate on a new project based around uv. Use when Claude needs to create a new Python project, write Python code with tests, or work on Python development using test-driven development practices with the uv package manager.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/simonw/skills --skill uv-tdd命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | uv-tdd |
| description | A development process for Python applications that uses TDD to iterate on a new project based around uv. Use when Claude needs to create a new Python project, write Python code with tests, or work on Python development using test-driven development practices with the uv package manager. |
A development process for Python applications that uses TDD to iterate on a new project based around uv.
Create a project with this command:
mkdir name-of-project
cd name-of-project
uv init
git init (if not already in a git repo)
This creates an initial pyproject.toml file
Add dependencies using:
uv add httpx
Always start by adding a dev dependency of pytest like this:
uv add pytest --dev
Then add a starting test:
mkdir tests
echo 'def test_add():
assert 1 + 1 == 2' > tests/test_add.py
Then run the tests like this:
uv run pytest
Always run Python code like this:
uv run python -c "..."
Always create a README.md for the project, which starts with just the project name as a heading plus a short description.
Start by creating a spec.md file with a detailed specification that includes markdown TODO lists. Update the spec and those TODOs as you progress, including adding new ones and checking off previous ones.
Practice TDD. For every change start by writing a test (grouped sensible in test files with other related tests) and then use uv run pytest -k name_of_test to watch it fail. Then implement the change and watch the test pass. Update the TODOs and add or update relevant documentation in the README, then commit the implementation and tests and documentation as a single commit.
Use and reuse pytest fixtures where appropriate, including for temporary files used for the duration of the test run. Use pytest.mark.parameterized to avoid duplicated test code.
Delete that test_add.py file once you have implemented your first real test. Do not include that test_add.py file in any of your commits.
Commit often, in sensible chunks. If a remote is configured then push after every commit.