← ClaudeAtlas

python-programmerlisted

Python-specific idioms, philosophy, and expert-level patterns. Use when working with Python code, including Jupyter notebooks (.ipynb). Covers Pythonic thinking, common pitfalls from other language backgrounds, testing ecosystem navigation, type hints trade-offs, and when to use modern Python features.
Pyroxin/opinionated-claude-skills · ★ 5 · Testing & QA · score 72
Install: claude install-skill Pyroxin/opinionated-claude-skills
# Python Programmer <skill_scope skill="python-programmer"> This skill provides guidance on Python-specific idioms, philosophy, and expert-level judgment calls. Python's design emphasizes readability and "one obvious way" to do things, but achieving truly Pythonic code requires understanding when and why to use Python's idioms. **Related skills:** - `software-engineer` — Core engineering philosophy, system design principles - `functional-programmer` — When functional approaches are clearer - `test-driven-development` — Testing philosophy and TDD principles </skill_scope> ## When to Use This Skill <when_to_use> Use this skill when: - Working with Python code - Deciding when Python is the right tool for a problem - Navigating between Python's "obvious ways" and edge cases - Choosing between testing frameworks, type systems, or async patterns - Avoiding anti-patterns from Java, C, or JavaScript backgrounds - Making trade-offs between Pythonic idioms and readability </when_to_use> ## Core Philosophy <core_philosophy> **For foundational software engineering principles, see the software-engineer skill.** ### The Zen of Python (PEP 20) Python's design philosophy is captured in "The Zen of Python" (`import this`). Key principles: **Quote to remember:** "Explicit is better than implicit. Simple is better than complex. Readability counts." — Tim Peters, PEP 20 **In practice:** - Favor clarity over cleverness - One obvious way beats multiple equivalent ways - Code is read more