domains / software-engineering / python-development / python-pro

python-pro

Skill card

combined

The three copies overlap on the goal of producing modern, type-safe, production-ready Python, but they are not interchangeable. Jeffallan/claude-skills is a concrete implementation skill with a strict workflow (mypy --strict, black, ruff, pytest >90% coverage), explicit MUST/MUST NOT constraints, code examples, and reference files. rmyndharis/antigravity-skills and sickn33/agentic-awesome-skills are nearly identical broad persona/capability skills targeting Python 3.12+ with uv, ruff, pydantic, FastAPI, and a 4-step high-level instruction set. Crowning one would hide a real alternative: the first is a procedural checklist, while the other two are a capability profile. They also disagree on the target Python version (3.11+ vs 3.12+) and on tooling emphasis (black + ruff vs ruff replacing black, plus uv).

Repositories

Other copies

Combined skill

---
name: python-pro
description: Use when building modern Python 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 ruff (and black where required). Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error handling.
---

# Python Pro

Modern Python 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 modern project structure (pyproject.toml)
- Performance optimization and profiling

## Do Not Use This Skill When

- You need guidance for a non-Python stack
- You only need basic syntax tutoring
- You cannot modify Python runtime or dependencies

## Core Workflow

1. **Analyze codebase** — Review structure, dependencies, type coverage, test suite. Confirm runtime, dependencies, and performance targets.
2. **Design interfaces** — Define protocols, dataclasses, type aliases. Choose patterns (async, typing, tooling) that match requirements.
3. **Implement** — Write Pythonic code with full type hints and error handling.
4. **Test** — Create comprehensive pytest suite with >90% coverage.
5. **Validate** — Run `mypy --strict`, `ruff`, and `black` (if the project uses black).
   - 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.
6. **Profile and tune** — Profile for latency, memory, and correctness; tune as needed.

## Constraints

### MUST DO
- Type hints for all function signatures and class attributes
- PEP 8 compliance with black formatting (or ruff format where black is not used)
- 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)

## Tooling Notes

- Use `uv` for package management when available; otherwise use pip/poetry.
- Use `ruff` for linting and formatting; use `black` if the project already depends on it.
- Use `mypy --strict` for static type checking.
- Use `pytest` with fixtures, mocking, and parametrize for testing.

## Output Templates

When implementing Python features, provide:
1. Module file with complete type hints
2. Test file with pytest fixtures
3. Type checking confirmation (mypy --strict passes)
4. Brief explanation of Pythonic patterns used

## Conflicts

- **Jeffallan/claude-skills** targets Python 3.11+ and mandates black formatting alongside ruff. **rmyndharis/antigravity-skills** and **sickn33/agentic-awesome-skills** target Python 3.12+ and position ruff as replacing black, isort, and flake8. This combined skill supports both: use black if the project requires it, otherwise use ruff format.
- **Jeffallan/claude-skills** provides a detailed 5-step workflow with explicit validation gates. **rmyndharis/antigravity-skills** and **sickn33/agentic-awesome-skills** provide a 4-step high-level instruction set. This combined skill merges both: the detailed workflow is the primary procedure, and the high-level steps are folded into it.
- **Jeffallan/claude-skills** includes explicit MUST DO / MUST NOT constraints and code examples. **rmyndharis/antigravity-skills** and **sickn33/agentic-awesome-skills** list capabilities and behavioral traits without those hard constraints. This combined skill retains the hard constraints from Jeffallan/claude-skills and the capability breadth from the other two.