ludo-technologies/python-best-practices

Python best practices Skill for AI coding agents

30Stars on the repository
4Mods indexed here, across every type
1mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

coding-standards

01

ludo-technologies/python-best-practices

Skill Claude Code

Python coding standards and best practices covering error handling, performance optimization, async patterns, SOLID design principles, documentation, data validation, and object-oriented programming. Use when writing, reviewing, or refactoring Python code, or when the user asks about Python style, design, or best…

not rated 30 1mo ago A SkillSpector: pass 63 tokens original MIT

testing

02

ludo-technologies/python-best-practices

Skill Claude Code

Python test-writing best practices covering test structure, fixtures, parametrization, and mocking with pytest. Use when writing, reviewing, or refactoring tests, adding test coverage, or working in tests directories and conftest.py.

not rated 30 1mo ago A SkillSpector: pass 47 tokens original MIT

tooling

03

ludo-technologies/python-best-practices

Skill Claude Code

Python development tooling configuration and best practices for ruff, mypy, pytest, pyscn, and uv. Use when setting up a Python project, configuring linters, formatters, type checkers, or test frameworks, or when editing pyproject.toml or tool config files.

not rated 30 1mo ago A SkillSpector: pass 60 tokens original MIT

data-science

04

ludo-technologies/python-best-practices

Skill Claude Code

NumPy and pandas best practices for data science and ML code covering vectorization, DataFrame indexing and mutation under Copy-on-Write, dtypes, schema validation with pandera, reproducible randomness, transformation style, array typing, and numeric testing. Use when writing, reviewing, or refactoring code that uses…

not rated 30 1mo ago A SkillSpector: pass 98 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: