python-project

name	python-project
description	Use for Python repo scaffolding and hardening: pyproject/setuptools-scm, src layout, Ruff, pytest, Typer, Pydantic, CLI tools, systemd services, APIs/UI apps, and Python project CI. Do not use for domain-specific Nebius automation, Terraform modules, Helm charts, or generic non-Python projects.

Python Project

Scaffold production-grade Python repositories with conservative, reusable defaults.

Use This Skill For

• Creating a new Python project from scratch.
• Standardizing an existing Python repo layout and tooling.
• Adding or improving:
  • CLI applications
  • systemd services/timers
  • API services and UI apps
  • IaC and automation integration
  • security and networking controls
  • AI/ML pipelines and model-serving structure

Defaults

• pyproject.toml with PEP 621 metadata.
• Prefer pyproject.toml as the single packaging metadata source; add a minimal setup.py shim only when repo policy, legacy build entrypoints, or release tooling still require python setup.py compatibility.
• setuptools + setuptools-scm for build/versioning.
• src/ package layout.
• If the package exposes __version__, a runtime resolver that prefers live SCM state in source checkouts and falls back to metadata/generated version files for installed artifacts.
• ruff for linting/formatting checks.
• pytest for tests.
• Split test layout:
  • tests/unit/ for fast local development tests.
  • tests/integration/ for isolated release/CI validation.
  • tests/conftest.py for shared fixtures and network guards.
• Typer + Rich for CLI UX.
• Pydantic for config/schema validation.
• Makefile with .DEFAULT_GOAL := all and aggregate all target (for example all: check build).
• CI pattern:
  • Pull requests: lint, fast unit tests, build.
  • Release/manual runs: lint, unit, integration, coverage, packaging.
• Optional packaged systemd assets in src/<package>/systemd/.

Workflow

1. Gather missing essentials only:
   • Project name (distribution) and import package name.
   • Python version range (default: >=3.11,<3.14).
   • Workload profile(s): cli, systemd, api, ui, iac, automation, security, networking, ai-ml.
   • Runtime target (local VM, container, Kubernetes, hybrid).
2. Start from:
   • references/base-layout.md
   • references/testing.md
   • assets/pyproject.toml.template
   • assets/Makefile.template
   • assets/tests-conftest.py.template
3. Load only relevant profile references:
   • references/cli-systemd.md
   • references/api-ui.md
   • references/iac-automation-security-networking.md
   • references/ai-ml.md
   • references/testing.md when adding or standardizing tests
4. Generate scaffolding and output in this order:
   • Directory tree
   • Full file contents (one file at a time)
   • Exact bootstrap/lint/test/build/run commands
   • Security + operations checklist
5. Keep placeholders (TODO) for environment-specific values and never invent secrets.

Output Contract

Always include:

• pyproject.toml
• .gitignore
• README.md
• src/<package>/__init__.py
• src/<package>/__main__.py
• tests/conftest.py
• tests/unit/
• tests/integration/

Add these when selected:

• cli: src/<package>/cli.py and [project.scripts].
• systemd: src/<package>/systemd/*.service and optional *.timer, plus package-data configuration.
• api: src/<package>/api.py (ASGI app) and production run guidance.
• ui: src/<package>/ui.py and auth/network boundary notes.
• iac: infra/terraform/ (or point to $terraform skill for full scaffolding).
• automation: Makefile, .github/workflows/ci.yml, .pre-commit-config.yaml.
  • Makefile must set .DEFAULT_GOAL := all.
  • Makefile must include an all target that aggregates primary checks/build.
  • Makefile should expose test-unit, test-integration, and coverage.
  • CI should keep PR validation fast and move integration/coverage to release or manual runs.
• ai-ml: src/<package>/ml/ split for train/eval/infer pipelines.

Learning Loop

When using this skill, capture durable, reusable, public-safe learnings back into this skill's local source materials before completion when the current task contract allows source edits. Update the narrowest appropriate surface: SKILL.md for runtime rules, references/ for detailed guidance, assets/ for reusable templates, scripts/ for deterministic helpers, and README or changelog entries for human-facing or release-note updates.

If the current task is explicitly read-only/report-only, or source writes are outside this skill's task contract, do not edit skill sources; report the skipped source update instead.

Do not capture secrets, private URLs, customer data, raw logs, one-off local state, or unverified/vendor-specific claims. If a useful learning is not safe, not evidence-backed, or outside this skill's scope, report that it was skipped.

Non-Negotiable Guardrails

• No secret material in repo, samples, logs, tests, or docs.
• Ignore runtime, build, cache, credential, and local config artifacts.
• Prefer bounded dependency ranges (>=x,<y) and avoid unconstrained pins unless required.
• Keep commands idempotent where practical.
• Use typed boundaries for external inputs (Pydantic models/dataclasses).
• Return explicit non-zero exit codes for CLI failures.
• Avoid shelling out when a Python API exists; if shell is required, set explicit timeouts and sanitize args.
• Keep networking code timeout-safe and retry-safe.
• Unit tests must not access the network, real cloud APIs, or external infrastructure.
• Integration tests must be explicitly marked and isolated from the fast unit lane.
• Prefer patching external clients with unittest.mock.patch in unit tests.
• Keep fixtures small and deterministic; avoid large datasets in default scaffolds.

Versioning and Release Pattern

Default to setuptools-scm with SemVer tags:

• Tag format: <project>-vMAJOR.MINOR.PATCH
• If the package exports __version__, do not import the generated _version.py file directly from __init__.py for source/editable checkouts. Prefer a runtime_version.py helper that tries live SCM state first, then package metadata, then the generated version file.
• Generated runtime version file: src/<package>/_version.py
• Do not manually edit the version in pyproject.toml when SCM versioning is enabled.

For containerized/Helm-delivered apps, keep version layers related but independent:

• App version (source of functional behavior):
  • SemVer from tags.
• Image version (source of deployed artifact):
  • publish immutable tags (sha-<shortsha>, and release tags like X.Y.Z + X.Y.Z-g<shortsha>).
  • prefer production deploys pinned by digest.
• Helm chart versioning:
  • Chart.yaml.version tracks chart packaging changes.
  • Chart.yaml.appVersion tracks the default app/image SemVer.
  • do not force chart version to equal app SemVer.

Templates and References

• assets/pyproject.toml.template: baseline project metadata and tooling.
• assets/cli.py.template: Typer-based CLI starter.
• assets/api.py.template: FastAPI starter with health endpoint.
• assets/systemd.service.template: hardened service unit baseline.
• assets/Makefile.template: local developer workflow and fast test targets.
• assets/tests-conftest.py.template: pytest fixture baseline with unit-test network blocking.
• assets/test-cli.py.template: sample unit tests for a Typer CLI.
• assets/test-integration-cli.py.template: sample integration smoke test layout.
• assets/github-actions-ci.yml.template: CI with fast PR checks and fuller release/manual validation.

Use detailed references only when needed:

• references/base-layout.md
• references/cli-systemd.md
• references/api-ui.md
• references/iac-automation-security-networking.md
• references/ai-ml.md
• references/testing.md