plugins/python-engineering/skills/python3-tools/SKILL.md
Use when working with Python tooling — uv package management, Hatchling build backend, ty or mypy type checker configuration, ruff linting, pre-commit hook setup, TOML read-write with tomlkit or tomllib, or PyPI packaging and release workflows. Routes to standalone specialist skills for deep dives on any single tool.
npx skillsauth add jamie-bitflight/claude_skills python3-toolsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Consult python3-core for standing defaults.
uv add for dependencies (not uv pip install)uv run for execution (not source .venv/bin/activate)uv sync --frozen for CI; uv sync --locked to detect stale lockfiles#!/usr/bin/env -S uv --quiet run --active --scriptuv venv --clear to overwrite existing environments (since 0.10.0)Check .pre-commit-config.yaml → CI config → pyproject.toml:
[tool.mypy]; do not force ty[tool.mypy] alone (may be stub config)Hatchling preferred:
[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"
[tool.hatch.build.targets.wheel]
packages = ["src/my_package"]
Detect installed tool: read .git/hooks/pre-commit line 2 to identify pre-commit vs prek. Both use the same config file.
tomlkit for read/write (preserves formatting) — open in text modetomllib (stdlib) for read-only — tomllib.load() requires binary mode ("rb"), tomllib.loads() takes a string# pyproject.toml
[project]
name = "my-package"
version = "0.1.0"
requires-python = ">=3.11"
classifiers = ["Typing :: Typed"]
[project.scripts]
my-cli = "my_package.cli:app"
Load these skills when the task is focused entirely on one tool:
python-engineering:uv when the task involves uv commands, lockfiles, PEP 723 scripts, workspace configuration, Python version management, CI/CD integration, Docker setup with uv, or migration from pip/poetry/pyenv.python-engineering:ty when the task involves running ty type checks, configuring ty.toml or [tool.ty], suppressing diagnostics, interpreting ty error codes, ty editor integration, or migrating from mypy/pyright to ty.python-engineering:hatchling when the task involves Hatchling build hooks, custom builders, wheel/sdist configuration, editable installs, VCS version sources, PEP 517/518/621/660 compliance, or setuptools migration.python-engineering:toml-python when the task requires advanced TOML manipulation: comment-preserving read-modify-write, atomic config updates, tomlkit API patterns, or XDG config file management.python-engineering:pre-commit when the task requires configuring hook stages, writing .pre-commit-hooks.yaml definitions, implementing prepare-commit-msg hooks, or distributing a tool as a pre-commit hook.python-engineering:pypi-readme-creator when the task involves creating or validating a PyPI README, choosing between Markdown and RST formats, configuring readme in pyproject.toml, or running twine check.references/tooling-defaults.md — full tooling referencereferences/compatibility-lanes.md — version compatibilitydevelopment
When an application needs to store config, data, cache, or state files. When designing where user-specific files should live. When code writes to ~/.appname or hardcoded home paths. When implementing cross-platform file storage with platformdirs.
testing
Enforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Use this skill when about to execute implementation actions (Bash, Write, Edit) to verify hypothesis-action alignment. Blocks execution when hypothesis unverified or action targets different system than hypothesis identified. Critical for preventing cognitive dissonance where correct diagnosis leads to wrong implementation.
tools
Reference guide for the Twelve-Factor App methodology — 15 principles (12 original + 3 modern extensions) for building portable, resilient, cloud-native applications. Use when evaluating application architecture, designing cloud-native services, reviewing codebases for methodology compliance, advising on configuration, scaling, observability, security, and deployment patterns. Incorporates the 2025 open-source community evolution and cloud-native reinterpretations of each factor.
tools
Converts user-facing documentation (how-to guides, tutorials, API references, examples) in any format — Markdown, PDF, DOCX, PPTX, XLSX, AsciiDoc, RST, HTML, Jupyter notebooks, man pages, TOML/YAML/JSON configs, and plain text — into Claude Code skill directories with SKILL.md plus thematically grouped references/*.md files. Use when given a docs directory or mixed-format documentation to transform into an AI skill. Uses MCP file-reader server for binary formats.