Agent skill
python-patterns
Python development patterns including package manager detection (uv, poetry, pip), project structure, and idiomatic Python practices. Use when writing, reviewing, or debugging Python application code. Do NOT use for test code -- use python-testing instead.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/python-patterns-cooldaemon-dotfiles
SKILL.md
Python Development Patterns
Package Manager Detection (CRITICAL)
Before running ANY Python commands, detect the package manager:
| File | Package Manager | Prefix |
|---|---|---|
uv.lock |
uv | uv run |
poetry.lock |
poetry | poetry run |
Pipfile.lock |
pipenv | pipenv run |
| None | pip | python -m |
NEVER use pip install directly when lock file exists.
Project Structure
project/
├── mypackage/ # NOT src/mypackage/
│ ├── __init__.py
│ ├── __main__.py # Entry point for python -m mypackage
│ ├── cli.py # CLI argument parsing
│ ├── core.py # Business logic
│ └── utils.py # Helpers
├── tests/
├── pyproject.toml
├── uv.lock
└── Makefile
Flat layout (mypackage/) is preferred over src layout (src/mypackage/).
CLI Structure (CRITICAL)
Three-layer separation:
# mypackage/__main__.py - Minimal bootstrap
if __name__ == "__main__":
from mypackage.cli import main
main()
# mypackage/cli.py - CLI argument parsing only
import argparse
from mypackage.core import process_data
def main():
parser = argparse.ArgumentParser()
parser.add_argument("input")
args = parser.parse_args()
result = process_data(args.input)
print(result)
# mypackage/core.py - Business logic (testable without CLI)
def process_data(input_path: str) -> str:
...
Why:
python -m mypackageworks via__main__.py- Core logic is testable without invoking CLI
- Easier to reuse as library
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?