Python Best Practices
Python development best practices including PEP 8 style guidelines, type hints, docstring conventions, and common patterns. Use when writing or modifying Python code.
Install
npx skills add jefflester/claude-skills-supercharged --skill python-best-practicesgit clone --depth 1 https://github.com/jefflester/claude-skills-supercharged.git /tmp/claude-skills-supercharged
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-supercharged/.claude/skills/python-best-practices ~/.claude/skills/python-best-practicesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Python Best Practices ## Purpose This skill provides guidance on Python development best practices to ensure code quality, maintainability, and consistency across your Python projects. ## When to Use This Skill Auto-activates when: - Working with Python files (*.py) - Mentions of "python", "best practices", "style guide" - Adding type hints or docstrings - Code refactoring in Python ## Style Guidelines ### PEP 8 Compliance Follow PEP 8 style guide for Python code: - **Indentation**: 4 spaces per indentation level - **Line Length**: Maximum 79 characters for code, 72 for docstrings/comments - **Blank Lines**: 2 blank lines between top-level definitions, 1 between methods - **Imports**: Always at top of file, grouped (stdlib, third-party, local) - **Naming Conventions**: - `snake_case` for functions, variables, modules - `PascalCase` for classes - `UPPER_SNAKE_CASE` for constants - Leading underscore `_name` for internal/private ### Import Organization Always organize imports in this order: ```python # 1. Standard library imports import os import sys from pathlib import Path # 2. Third-party imports import requests import numpy as np # 3. Local application imports from myapp.core import MyClass from myapp.utils import helper_function ``` Avoid circular imports by using `TYPE_CHECKING`:
Details
- Skill name
python-best-practices- Repository
- jefflester/claude-skills-supercharged
- Path
.claude/skills/python-best-practices/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Python Best Practices skill do?
Python development best practices including PEP 8 style guidelines, type hints, docstring conventions, and common patterns. Use when writing or modifying Python code.
How do I install the Python Best Practices skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jefflester/claude-skills-supercharged --skill python-best-practices. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Python Best Practices popular?
It lives in jefflester/claude-skills-supercharged, which has 43 GitHub stars and 3 forks.
Related skills
Skill Developer
43jefflester/claude-skills-supercharged
Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, keyword triggers, hook mechanisms (UserPromptSubmit), session tracking, and the 500-line rule.
API Security
43jefflester/claude-skills-supercharged
API security best practices and common vulnerability prevention. Enforces security checks for authentication, input validation, SQL injection, XSS, and OWASP Top 10 vulnerabilities. Use when building or modifying APIs.
Git Workflow
43jefflester/claude-skills-supercharged
Git workflow best practices including commit messages, branching strategies, pull requests, and collaboration patterns. Use when working with Git version control.
Golang Backend
47mujez/claude-skills
Expert Go backend engineer skill. Use when writing Go services, APIs, microservices, CLI tools, or libraries. Covers architecture, concurrency, testing, database patterns, gRPC, REST APIs, error handling, and Go best practices.
Poc
49Dan-Cleary/fdestack
Build a throwaway proof-of-concept. Speed over quality. Hardcoded values OK, ugly code OK, no error handling beyond crash prevention. This code is NEVER going to production — /integrate will rebuild fresh. The skill's most important step is the learnings write-back at the end, which routes discoveries to stack.md / decisions.md / learnings.jsonl so /integrate can use them without ever reading POC code. Proactively invoke this skill after /scope when the FDE says "let me build a quick thing", "let me try this", "time to prototype", "let's hack something together", or otherwise indicates they're
Interface Auditor
32uxuiprinciples/agent-skills
Detect UX antipatterns (smells) in interface descriptions using the uxuiprinciples smell taxonomy. Returns structured findings with matched symptoms, severity, and step-by-step remediation recipes. API key optional — full remediation recipes require uxuiprinciples.com API Access.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.