What problem does it solve? Structuring a Python project for publication involves many conventions — pyproject.toml metadata, src layout, semantic versioning, build backends, and PyPI release steps — that are easy to get wrong or inconsistent across projects. This Skill encodes those conventions so a package meets PyPI publishing standards on the first attempt. ## Core Features & Use Cases - Canonical package layout: Enforces a standard structure with src layout, pyproject.toml, tests, docs, LICENSE, and CHANGELOG. - Build and release workflow: Covers hatchling build configuration, semantic versioning with hatch, uv build, twine checks, and publishing to PyPI or TestPyPI. - Public API and quality gates: Defines init.py export rules, py.typed type-hint shipping, and a pre-release check sequence (ruff, mypy, pytest, build, twine). - Use Case: You have a working Python script collection and want to publish it as a package on PyPI. This Skill restructures it into src layout, writes compliant pyproject.toml metadata, sets up versioning, and walks through building and publishing the wheel. ## Quick Start Ask Claude to create a new publishable Python package named 'mypackage' with src layout and pyproject.toml configured for PyPI release.
