Python code can be messy without consistent rules. This guide helps you set up tools like ruff and mypy to automatically enforce style and quality. You will learn PEP 8 naming, import organization, and how to write clear docstrings.
By following these patterns, your team can focus on logic instead of formatting debates. Type hints make code safer and easier to understand. Use this skill when starting a new project or reviewing pull requests.
Global
mkdir -p ~/.claude/skills/python-code-styleProject
mkdir -p .claude/skills/python-code-styleSource Repository
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective
Auditpbakaus/impeccable
Audit your code for accessibility performance theming and anti-patterns
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues