python

Standardize Python project conventions with uv, ruff, pyright, and pytest.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/pantry --skill python-dotbeeps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python
Source: https://github.com/dotBeeps/pantry/tree/main/morsels/skills/python
Command: npx skills add https://github.com/dotBeeps/pantry --skill python-dotbeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Python conventions: uv tooling, typing, project structure. Use when working with Python source files or pyproject.toml.

Core Features & Use Cases

  • uv tooling setup and standard project scaffolding for Python projects
  • enforce typing and style with pyright and ruff
  • maintain a consistent 4-space formatting, naming conventions, and pyproject.toml baseline

Quick Start

Configure your Python project workspace with uv init and follow the conventions in this guide.

Frequently Asked Questions about python

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

FAQPage Schema
How do I set up a Python project structure with uv and pyproject.toml?

Standardizing Python project conventions with uv requires initializing via uv init and configuring a pyproject.toml baseline. This enforces 4-space formatting, typing discipline, and consistent project structure across Python codebases of all sizes.

What's the best way to enforce typing and style in a Python project?

The best way to enforce typing and style in a Python project is configuring pyright and ruff within your pyproject.toml. These tools maintain typing discipline, enforce 4-space formatting, and ensure consistent naming conventions across your codebase.

Do I need uv and pyright to maintain consistent Python project conventions?

Yes, uv and pyright are required tooling to maintain consistent Python project conventions. Enforcing these tools alongside ruff and pytest reduces setup time and ensures standard formatting, typing, and project structure across Python source files.

Can I apply standard Python tooling conventions to existing codebases?

Yes, you can apply standard Python tooling conventions to existing codebases for ongoing maintenance. Configuring uv, ruff, pyright, and pytest enforces a 4-space formatting standard and pyproject.toml baseline across Python projects of all sizes.

Why standardize Python project structure with uv instead of manual configuration?

Standardizing Python project structure with uv instead of manual configuration reduces setup time and improves consistency. It enforces tooling requirements, typing discipline, and a pyproject.toml baseline, eliminating the need to manually manage formatting and style rules.