python-pypi-setup

Publishing to PyPI requires a modern `pyproject.toml` configuration, `src/` directory structure, and build tools like `build` and `twine`. This Skill automates the entire setup—generating the configuration file, directory layout, and a `build-publish.sh` script so you can publish with a single command after authentication.

`pyproject.toml` is the modern Python packaging standard (PEP 517/518) that replaces legacy `setup.py`. It defines project metadata, dependencies, and build requirements in a single file. This Skill generates a fully compliant `pyproject.toml` so your package follows current best practices and works with modern tooling.

The `src/` layout is the recommended structure for Python packages—it isolates your package code from tests and configuration. This Skill automatically creates the `src/` directory structure with your package, avoiding manual setup and ensuring proper package discovery during builds and publishing.

Yes. This Skill generates a `build-publish.sh` script that automates the entire workflow: it builds your distribution files using the `build` tool and uploads them to PyPI using `twine`. After setup, you run one command to publish instead of juggling multiple tools manually.

A production-ready Python package needs `pyproject.toml` for metadata and build config, a `src/` layout for code, `LICENSE` and `README.md` for documentation, `.gitignore` to exclude build artifacts, and `dev-requirements.txt` for development dependencies. This Skill generates all of these in one step with guided prompts.

You'll provide your project name, package name, author details, GitHub username, license type, Python version, dependencies, and keywords through interactive prompts. This Skill uses that metadata to populate `pyproject.toml`, `README.md`, and other files automatically, eliminating manual typing and configuration errors.