domains / families / software-engineering / python-pro

python-pro

combined

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. Master Python 3.12+ with modern features, async programming,

When to use

• 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
• Writing or reviewing Python 3.12+ codebases
• Implementing async workflows or performance optimizations

When not to use

• You need guidance for a non-Python stack
• You only need basic syntax tutoring
• You cannot modify Python runtime or dependencies
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

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).