modern-python-standards

Enforce Python 3.11+ typing, pathlib, dataclass, and Google-style docstring standards.

4|2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/nick-orton/vybz --skill modern-python-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: modern-python-standards
Source: https://github.com/nick-orton/vybz/tree/main/src/vybz/library/skills/modern-python-standards
Command: npx skills add https://github.com/nick-orton/vybz --skill modern-python-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies modern Python development practices, improving reliability, readability, and maintainability across projects.

Core Features & Use Cases

  • Enforce Python 3.11+ typing discipline (PEP 585/604) and strict type hints.
  • Guide usage of pathlib for file system operations and @dataclass for data modeling.
  • Require Google-style docstrings and clear, self-documenting code across modules.
  • Apply consistent coding standards across libraries, services, and tooling.

Quick Start

Initialize a Python 3.11+ project and apply the modern-python-standards guidelines to ensure idiomatic, type-safe code.

Frequently Asked Questions about modern-python-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce modern Python typing standards in my project?▼

Enforce modern Python typing standards by applying strict type hints using PEP 585/604 syntax for Python 3.11+ projects. This ensures type-safe code organization, reliable refactoring, and consistent dataclass patterns across libraries and services.

What are the best practices for organizing Python 3.11+ code with dataclasses and pathlib?▼

Best practices for modern Python code involve using pathlib for all file system operations and @dataclass patterns for data modeling. These standards improve readability and maintainability while ensuring safe, self-documenting code across modules.

Does this approach support Google-style docstrings for Python services?▼

Yes, this approach requires Google-style docstrings across Python modules to ensure clear documentation. Applying these coding standards to libraries, services, and tooling guarantees consistent, self-documenting code that meets modern reliability requirements.

Can I apply strict type safety to existing Python libraries and tooling?▼

Yes, you can apply strict type safety to existing Python libraries and tooling. The guidelines specify safe refactoring patterns to modernize codebases, ensuring idiomatic Python 3.11+ practices without breaking current functionality.

When do I need strict type hints and PEP 585 syntax for Python development?▼

You need strict type hints and PEP 585 syntax when developing or refactoring Python 3.11+ projects. Implementing this typing discipline prevents runtime errors and codifies modern practices for robust data modeling and reliable code execution.