wfc-python

Define Python 3.12+ development standards for WFC projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sam-fakhreddine/wfc --skill wfc-python
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wfc-python
Source: https://github.com/sam-fakhreddine/wfc/tree/main/wfc/skills/wfc-python
Command: npx skills add https://github.com/sam-fakhreddine/wfc --skill wfc-python

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-dotenv>=1.0, orjson>=3.9, structlog>=24.1, tenacity>=8.2, pydantic>=2.6, pydantic-settings>=2.2, httpx>=0.27, joblib>=1.3, fastapi>=0.110, uvicorn>=0.27, fire>=0.5, faker>=22.0, pytest>=8.0, pytest-cov>=4.1, pytest-asyncio>=0.23, and includes scripts (resource) components.

What problem does it solve?

This Skill enforces a consistent, high-quality standard for Python development within WFC projects, ensuring maintainability, security, and performance across all Python codebases.

Core Features & Use Cases

  • Standardized Tooling: Enforces the use of UV, Black, Ruff, and Mypy for a streamlined development workflow.
  • Modern Python Practices: Mandates Python 3.12+ features, full type annotations, and PEP 562 for efficient imports.
  • Preferred Libraries & Frameworks: Promotes the use of battle-tested libraries like orjson, structlog, httpx, FastAPI, and Pydantic.
  • Use Case: When starting a new Python service, this Skill ensures all code adheres to best practices, reducing onboarding time and preventing common errors.

Quick Start

Ensure all new Python files adhere to the standards defined in the wfc-python skill.

Frequently Asked Questions about wfc-python

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

FAQPage Schema
What are the required Python development standards for WFC projects?

Python development standards for WFC require Python 3.12+, full type annotations, Black formatting, PEP 562 lazy imports, and specific preferred libraries like FastAPI, Pydantic, and structlog to ensure maintainability and performance.

How do I set up a Python toolchain using UV, Black, Ruff, and Mypy?

To set up your Python toolchain, enforce UV, Black, Ruff, and Mypy to streamline development workflows. This combination ensures standardized formatting, linting, and strict type checking across all WFC Python codebases.

Which Python libraries are preferred for WFC development over standard alternatives?

Preferred Python libraries for WFC development include orjson for JSON, structlog for logging, httpx for HTTP, FastAPI for APIs, and Pydantic for data validation, replacing standard alternatives to enhance performance and security.

Does this Python standard enforce type annotations and ban specific code patterns?

Yes, the Python standard enforces full type annotations and includes banned patterns for automated code scanning. This ensures strict adherence to universal code standards and prevents common development errors.

Can I use older Python versions with these WFC Python development standards?

No, you cannot use older Python versions. The WFC Python standards mandate Python 3.12+ syntax to leverage modern language features and ensure consistent, high-quality code across all projects.

Why should I use Pydantic and httpx in my Python services?

You should use Pydantic and httpx because they are battle-tested libraries promoted by WFC standards. Pydantic ensures robust data validation while httpx provides efficient HTTP client functionality for modern Python services.