Which build backends are supported?

It primarily recommends and configures Hatchling for new projects, but also provides support for modern Setuptools configurations when required.

Why does this skill enforce the src/ layout?

The src/ layout is a best practice that prevents accidental imports from the local directory and ensures your tests run against the actual installed version of your package.

Does it support Python monorepos?

Yes, the skill includes specific rules and configurations for managing multiple packages within a single repository using uv workspaces.

Can I still use setup.py with this skill?

No, this skill actively discourages legacy files like setup.py and setup.cfg, migrating all configuration to the modern, standardized pyproject.toml format.

Python Packaging & UV Conventions

Name: Python Packaging & UV Conventions
Author: jsamuelsen11

byjsamuelsen11

0•

Developer Tools

Standardizes Python project packaging using pyproject.toml and the uv package manager for modern, reproducible builds.

This skill provides Claude with a comprehensive set of conventions for modern Python development, emphasizing the 'src/' layout and the consolidation of all project configuration into pyproject.toml. It eliminates legacy files like setup.py and requirements.txt while leveraging the high-performance uv tool for dependency management. Perfect for developers starting new projects or migrating legacy codebases, this skill ensures best practices for versioning, CLI entry points, and workspace configurations are followed automatically.

Key Features

010 GitHub stars

02Configures modern build backends including Hatchling and Setuptools

03Provides optimized uv workflows for dependency resolution and locking

04Implements industry-standard src/ layout for robust package distribution

05Enforces pyproject.toml as the canonical source for all project configuration

06Standardizes tool settings for Ruff, MyPy, Pytest, and Coverage reporting

Use Cases

01Migrating legacy projects from setup.py and requirements.txt to modern PEP 621 standards

02Managing complex monorepos using uv workspace configurations and shared lock files

03Initializing a new Python library or application with production-ready standards

Key Features

010 GitHub stars

02Configures modern build backends including Hatchling and Setuptools

03Provides optimized uv workflows for dependency resolution and locking

04Implements industry-standard src/ layout for robust package distribution

05Enforces pyproject.toml as the canonical source for all project configuration

06Standardizes tool settings for Ruff, MyPy, Pytest, and Coverage reporting

Use Cases

01Migrating legacy projects from setup.py and requirements.txt to modern PEP 621 standards

02Managing complex monorepos using uv workspace configurations and shared lock files

03Initializing a new Python library or application with production-ready standards