python-project-layoutlisted

# Outcome Produce a concrete, reviewable result for the workflow below without overstating what was observed, executed, or verified. ## Compatibility Portable across Claude Code, Codex, and OpenCode. The optional inspector requires Python 3.11 and reads local files only. Packaging commands depend on the project's selected build backend and are never installed or run implicitly. ## Use this skill when - A new Python library or application needs an intentional repository and package layout. - Imports behave differently in the checkout, editable install, wheel, or test environment. - Legacy packaging files need consolidation into an authoritative `pyproject.toml`. - Package discovery, data files, type markers, namespace packages, or entry points may be wrong. - A layout or import-boundary change also requires unit, integration, or package-install tests to be redesigned; also use `python-test-architecture`. ## Do not use this skill when - The repository layout is settled and the task is to design unit, integration, or end-to-end tests; use `python-test-architecture`. - The task is command names, flags, help, or CLI configuration precedence; use `python-cli-command-design`. - The task is runtime service architecture, deployment topology, or framework selection. ## Inputs Inspect or obtain: - Relevant repository tree, excluding secrets and generated environments. - `pyproject.toml` and any `setup.py`, `setup.cfg`, manifest, lock, or tool configuration. - Repository, dis