python-best-practices
Python 3.13+ conventions for typed application and library boundaries. Use when writing or reviewing Python contracts, packages, validation, or async resource ownership.
Pinned to revision 7b151602dee1, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/python-best-practices/SKILL.md
- skills/python-best-practices/agents/openai.yaml
- skills/python-best-practices/references/async-context-managers.md
- skills/python-best-practices/references/async-pagination.md
- skills/python-best-practices/references/boundary-validation.md
- skills/python-best-practices/references/exception-handling.md
- skills/python-best-practices/references/finite-state-exhaustiveness.md
- skills/python-best-practices/references/inference-and-annotations.md
- skills/python-best-practices/references/naming-and-src-layout.md
- skills/python-best-practices/references/no-fabricated-defaults.md
- skills/python-best-practices/references/no-import-path-mutation.md
- skills/python-best-practices/references/no-runtime-asserts.md
- skills/python-best-practices/references/optional-narrowing.md
- skills/python-best-practices/references/pep-695-generics.md
- skills/python-best-practices/references/project-metadata.md
- skills/python-best-practices/references/protocols.md
- skills/python-best-practices/references/public-exports.md
- skills/python-best-practices/references/py-typed-and-stubs.md
Every link opens the file at its source, pinned to the revision this page describes.