python-code-devlisted

# Python Code Development ## Purpose Build maintainable, importable Python packages with a strict typed, class-first foundation. Classes are the default boundary for state, lifecycle, I/O, and domain behavior. Use pure functions only for small stateless transforms where a class would add ceremony. Keep business logic testable and separate from entrypoints. ## Workflows | Command | Action | |---|---| | `/python-code-dev new <project-name>` | Create a deterministic starter project | | `/python-code-dev adapt <path>` | Restructure existing Python code without changing behavior | | `/python-code-dev migrate <notebook.py>` | Move notebook logic into the package and update notebook imports | | `/python-code-dev verify <path>` | Run package, import, test, and quality checks | `new` is a script-only workflow. Do not hand-scaffold it. For `new`, run the skill script: ```bash bash /path/to/python-code-dev/scripts/new.sh "<project-name>" ``` Resolve `/path/to/python-code-dev` from the loaded skill location. If the harness exposes `AGENTS_SKILLS_DIR`, use `${AGENTS_SKILLS_DIR}/scripts/new.sh`; otherwise use the path shown in the skill header/location. If the script cannot be found, STOP and report the missing script. Do not manually create files as a fallback. If the current directory already looks like a project root (`.git`, `README.md`, `pyproject.toml`, `docs/`, or `.fleet/`), the script scaffolds in place as `./src/<package>/` and `./tests/`. Otherwise it creates `<project-