What problem does it solve? Splitting a Python repository into multiple packages often produces tangled cross-package imports, circular dependencies, and unclear public APIs, and uv workspaces cannot enforce import isolation between members. This Skill provides the architectural rules and wiring steps to structure a uv-workspace monorepo correctly. ## Core Features & Use Cases - Workspace wiring: Configures the root pyproject.toml with [tool.uv.workspace] members and [tool.uv.sources] workspace dependencies, with a single shared lockfile and --package targeting. - Dependency direction rules: Enforces an acyclic depend-inward graph where apps depend on the shared library, never on each other, with optional import-linter contracts for CI enforcement. - Safe extraction: Provides a safety-net-first sequence for carving a shared library out of an existing package while keeping the test suite green. - Use Case: A CLI and a web API both need the same domain logic. Use this Skill to create a libs/core shared library member, wire both apps to depend on it, define its public API boundary, and extract the shared code without breaking existing tests. ## Quick Start Use the python-monorepo-architecture skill to split my Python repo into a uv workspace with a shared core library and two app members.
