Python Pro
Modern Python 3.11+ specialist focused on type-safe, async-first, production-ready code.
When to Use This Skill
- Writing type-safe Python with complete type coverage
- Implementing async/await patterns for I/O operations
- Setting up pytest test suites with fixtures and mocking
- Creating Pythonic code with comprehensions, generators, context managers
- Building packages with Poetry and proper project structure
- Performance optimization and profiling
Core Workflow
- Analyze codebase — Review structure, dependencies, type coverage, test suite
- Design interfaces — Define protocols, dataclasses, type aliases
- Implement — Write Pythonic code with full type hints and error handling
- Test — Create comprehensive pytest suite with >90% coverage
- Validate — Run
mypy --strict, black, ruff
- If mypy fails: fix type errors reported and re-run before proceeding
- If tests fail: debug assertions, update fixtures, and iterate until green
- If ruff/black reports issues: apply auto-fixes, then re-validate
Reference Guide
Load detailed guidance based on context:
| Topic |
Reference |
Load When |
| Type System |
references/type-system.md |
Type hints, mypy, generics, Protocol |
| Async Patterns |
references/async-patterns.md |
async/await, asyncio, task groups |
| Standard Library |
references/standard-library.md |
pathlib, dataclasses, functools, itertools |
| Testing |
references/testing.md |
pytest, fixtures, mocking, parametrize |
| Packaging |
references/packaging.md |
poetry, pip, pyproject.toml, distribution |
Constraints
MUST DO
- Type hints for all function signatures and class attributes
- PEP 8 compliance with black formatting
- Comprehensive docstrings (Google style)
- Test coverage exceeding 90% with pytest
- Use
X | None instead of Optional[X] (Python 3.10+)
- Async/await for I/O-bound operations
- Dataclasses over manual init methods
- Context managers for resource handling
MUST NOT DO
- Skip type annotations on public APIs
- Use mutable default arguments
- Mix sync and async code improperly
- Ignore mypy errors in strict mode
- Use bare except clauses
- Hardcode secrets or configuration
- Use deprecated stdlib modules (use pathlib not os.path)
Code Examples
Type-annotated function with error handling
from pathlib import Path
def read_config(path: Path) -> dict[str, str]:
"""Read configuration from a file.
Args:
path: Path to the configuration file.
Returns:
Parsed key-value configuration entries.
Raises:
FileNotFoundError: If the config file does not exist.
ValueError: If a line cannot be parsed.
"""
config: dict[str, str] = {}
with path.open() as f:
for line in f:
key, _, value = line.partition("=")
if not key.strip():
raise ValueError(f"Invalid config line: {line!r}")
config[key.strip()] = value.strip()
return config
Dataclass with validation
from dataclasses import dataclass, field
@dataclass
class AppConfig:
host: str
port: int
debug: bool = False
allowed_origins: list[str] = field(default_factory=list)
def __post_init__(self) -> None:
if not (1 <= self.port <= 65535):
raise ValueError(f"Invalid port: {self.port}")
Async pattern
import asyncio
import httpx
async def fetch_all(urls: list[str]) -> list[bytes]:
"""Fetch multiple URLs concurrently."""
async with httpx.AsyncClient() as client:
tasks = [client.get(url) for url in urls]
responses = await asyncio.gather(*tasks)
return [r.content for r in responses]
pytest fixture and parametrize
import pytest
from pathlib import Path
@pytest.fixture
def config_file(tmp_path: Path) -> Path:
cfg = tmp_path / "config.txt"
cfg.write_text("host=localhost\nport=8080\n")
return cfg
@pytest.mark.parametrize("port,valid", [(8080, True), (0, False), (99999, False)])
def test_app_config_port_validation(port: int, valid: bool) -> None:
if valid:
AppConfig(host="localhost", port=port)
else:
with pytest.raises(ValueError):
AppConfig(host="localhost", port=port)
mypy strict configuration (pyproject.toml)
[tool.mypy]
python_version = "3.11"
strict = true
warn_return_any = true
warn_unused_configs = true
disallow_untyped_defs = true
Clean mypy --strict output looks like:
Success: no issues found in 12 source files
Any reported error (e.g., error: Function is missing a return type annotation) must be resolved before the implementation is considered complete.
Output Templates
When implementing Python features, provide:
- Module file with complete type hints
- Test file with pytest fixtures
- Type checking confirmation (mypy --strict passes)
- Brief explanation of Pythonic patterns used
Knowledge Reference
Python 3.11+, typing module, mypy, pytest, black, ruff, dataclasses, async/await, asyncio, pathlib, functools, itertools, Poetry, Pydantic, contextlib, collections.abc, Protocol
Documentation
1---2name: python-pro3description: Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error handling.4license: MIT5metadata:6 source: https://skillmd.com/skills/jeffallan/python-pro7 author: https://github.com/Jeffallan8 version: "1.1.0"9 domain: language10 triggers: Python development, type hints, async Python, pytest, mypy, dataclasses, Python best practices, Pythonic code11 role: specialist12 scope: implementation13 output-format: code14 related-skills: fastapi-expert, devops-engineer15---1617# Python Pro1819Modern Python 3.11+ specialist focused on type-safe, async-first, production-ready code.2021## When to Use This Skill2223- Writing type-safe Python with complete type coverage24- Implementing async/await patterns for I/O operations25- Setting up pytest test suites with fixtures and mocking26- Creating Pythonic code with comprehensions, generators, context managers27- Building packages with Poetry and proper project structure28- Performance optimization and profiling2930## Core Workflow31321. **Analyze codebase** — Review structure, dependencies, type coverage, test suite332. **Design interfaces** — Define protocols, dataclasses, type aliases343. **Implement** — Write Pythonic code with full type hints and error handling354. **Test** — Create comprehensive pytest suite with >90% coverage365. **Validate** — Run `mypy --strict`, `black`, `ruff`37 - If mypy fails: fix type errors reported and re-run before proceeding38 - If tests fail: debug assertions, update fixtures, and iterate until green39 - If ruff/black reports issues: apply auto-fixes, then re-validate4041## Reference Guide4243Load detailed guidance based on context:4445| Topic | Reference | Load When |46|-------|-----------|-----------|47| Type System | `references/type-system.md` | Type hints, mypy, generics, Protocol |48| Async Patterns | `references/async-patterns.md` | async/await, asyncio, task groups |49| Standard Library | `references/standard-library.md` | pathlib, dataclasses, functools, itertools |50| Testing | `references/testing.md` | pytest, fixtures, mocking, parametrize |51| Packaging | `references/packaging.md` | poetry, pip, pyproject.toml, distribution |5253## Constraints5455### MUST DO56- Type hints for all function signatures and class attributes57- PEP 8 compliance with black formatting58- Comprehensive docstrings (Google style)59- Test coverage exceeding 90% with pytest60- Use `X | None` instead of `Optional[X]` (Python 3.10+)61- Async/await for I/O-bound operations62- Dataclasses over manual __init__ methods63- Context managers for resource handling6465### MUST NOT DO66- Skip type annotations on public APIs67- Use mutable default arguments68- Mix sync and async code improperly69- Ignore mypy errors in strict mode70- Use bare except clauses71- Hardcode secrets or configuration72- Use deprecated stdlib modules (use pathlib not os.path)7374## Code Examples7576### Type-annotated function with error handling77```python78from pathlib import Path7980def read_config(path: Path) -> dict[str, str]:81 """Read configuration from a file.8283 Args:84 path: Path to the configuration file.8586 Returns:87 Parsed key-value configuration entries.8889 Raises:90 FileNotFoundError: If the config file does not exist.91 ValueError: If a line cannot be parsed.92 """93 config: dict[str, str] = {}94 with path.open() as f:95 for line in f:96 key, _, value = line.partition("=")97 if not key.strip():98 raise ValueError(f"Invalid config line: {line!r}")99 config[key.strip()] = value.strip()100 return config101```102103### Dataclass with validation104```python105from dataclasses import dataclass, field106107@dataclass108class AppConfig:109 host: str110 port: int111 debug: bool = False112 allowed_origins: list[str] = field(default_factory=list)113114 def __post_init__(self) -> None:115 if not (1 <= self.port <= 65535):116 raise ValueError(f"Invalid port: {self.port}")117```118119### Async pattern120```python121import asyncio122import httpx123124async def fetch_all(urls: list[str]) -> list[bytes]:125 """Fetch multiple URLs concurrently."""126 async with httpx.AsyncClient() as client:127 tasks = [client.get(url) for url in urls]128 responses = await asyncio.gather(*tasks)129 return [r.content for r in responses]130```131132### pytest fixture and parametrize133```python134import pytest135from pathlib import Path136137@pytest.fixture138def config_file(tmp_path: Path) -> Path:139 cfg = tmp_path / "config.txt"140 cfg.write_text("host=localhost\nport=8080\n")141 return cfg142143@pytest.mark.parametrize("port,valid", [(8080, True), (0, False), (99999, False)])144def test_app_config_port_validation(port: int, valid: bool) -> None:145 if valid:146 AppConfig(host="localhost", port=port)147 else:148 with pytest.raises(ValueError):149 AppConfig(host="localhost", port=port)150```151152### mypy strict configuration (pyproject.toml)153```toml154[tool.mypy]155python_version = "3.11"156strict = true157warn_return_any = true158warn_unused_configs = true159disallow_untyped_defs = true160```161162Clean `mypy --strict` output looks like:163```164Success: no issues found in 12 source files165```166Any reported error (e.g., `error: Function is missing a return type annotation`) must be resolved before the implementation is considered complete.167168## Output Templates169170When implementing Python features, provide:1711. Module file with complete type hints1722. Test file with pytest fixtures1733. Type checking confirmation (mypy --strict passes)1744. Brief explanation of Pythonic patterns used175176## Knowledge Reference177178Python 3.11+, typing module, mypy, pytest, black, ruff, dataclasses, async/await, asyncio, pathlib, functools, itertools, Poetry, Pydantic, contextlib, collections.abc, Protocol179180[Documentation](https://jeffallan.github.io/claude-skills/skills/language/python-pro/)