python

Étoiles3

Forks1

Mis à jour23 juillet 2026 à 22:15

Python, pyproject.toml, uv, pip, pytest, Pydantic, type hints, or Python patterns.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

ilude

ilude/dotfiles

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

6 fichiers

SKILL.md

readonly

name	python
description	Python, pyproject.toml, uv, pip, pytest, Pydantic, type hints, or Python patterns.

Python Projects Workflow

Compact index for Python work. Load linked files only for framework-specific details or examples.

Project-specific rules

This repo uses uv, pytest, and ruff; Python floor is 3.9 from pyproject.toml.
Prefer explicit exceptions when required data/dependencies are missing; do not add silent fallback logic.
Keep scripts idempotent and LF-only.
Do not introduce broad try/except wrappers or guard flags unless requested.
Before resolving new dependencies, apply the uv supply-chain hardening settings from reference.md; prefer locked installs and avoid ad-hoc uv pip install.
In Bash commands, use python, not python3. Run script paths directly; use python -m only for modules.

Practical steps

Identify the Python project root and read pyproject.toml and relevant tests.
Use uv for dependency and command execution when the project supports it.

Quick validation

Purpose	Commands
Dotfiles quick tests	`make test-quick`
Python tests	`make test-pytest` or `uv run pytest <path>`
Python lint	`make lint-python` or `uv run ruff check <path>`
Format check/fix	`uv run ruff format --check <path>` / `uv run ruff format <path>`
Full repo check	`make check`

Anti-patterns

Using pip/global installs when uv is available in the repo workflow.
Adding comments that restate obvious Python syntax instead of explaining domain intent.
Broad exception swallowing, hidden defaults, or fallback behavior that masks missing data.
Changing public behavior without focused regression tests.

Optional references

reference.md - detailed guidance, examples, and templates.
testing.md - pytest patterns.
fastapi.md, flask.md, django.md - framework guidance.

Plus depuis ce dépôt

même dépôt

pi-extension

ilude/dotfiles

Pi extensions and tool policy: extensions/*.ts, hooks, registerTool, promptGuidelines, registerCommand, footer/status UI, tool_result, session hooks, or subprocesses. Not for slash-command placement; use pi-command.

2026-08-023

docs

ilude/dotfiles

README, CHANGELOG, docs/, RFCs, ADRs, guides, or Markdown structure. Not for prose cleanup or archival work.

2026-07-273

no-ai-slop

ilude/dotfiles

Prose cleanup for filler, hype, vague claims, repetition, detection tells, or uncited specifics. Not for Markdown architecture or archival work.

2026-07-273

planning

ilude/dotfiles

Requirements, user stories, acceptance/verification criteria, or testable outcomes. Not for PRD drafting (/prd) or Pi /goal prompts.

2026-07-273

prd

ilude/dotfiles

Use for /prd-it or to draft, refine, or review a Product Requirements Document. Not for acceptance criteria, planning, or Pi /goal prompts.

2026-07-273

pi-log-analytics

ilude/dotfiles

Pi session, trace, metrics, routing, workflow-friction, workflow-telemetry, usage, or local JSONL analysis with DuckDB. Use for aggregating or correlating Pi runtime logs. Not for adding telemetry, generic SQL/database design, or non-Pi logs.

2026-07-273

name	python
description	Python, pyproject.toml, uv, pip, pytest, Pydantic, type hints, or Python patterns.

Python Projects Workflow

Compact index for Python work. Load linked files only for framework-specific details or examples.

Project-specific rules

This repo uses uv, pytest, and ruff; Python floor is 3.9 from pyproject.toml.
Prefer explicit exceptions when required data/dependencies are missing; do not add silent fallback logic.
Keep scripts idempotent and LF-only.
Do not introduce broad try/except wrappers or guard flags unless requested.
Before resolving new dependencies, apply the uv supply-chain hardening settings from reference.md; prefer locked installs and avoid ad-hoc uv pip install.
In Bash commands, use python, not python3. Run script paths directly; use python -m only for modules.

Practical steps

Identify the Python project root and read pyproject.toml and relevant tests.
Use uv for dependency and command execution when the project supports it.

Quick validation

Purpose	Commands
Dotfiles quick tests	`make test-quick`
Python tests	`make test-pytest` or `uv run pytest <path>`
Python lint	`make lint-python` or `uv run ruff check <path>`
Format check/fix	`uv run ruff format --check <path>` / `uv run ruff format <path>`
Full repo check	`make check`

Anti-patterns

Using pip/global installs when uv is available in the repo workflow.
Adding comments that restate obvious Python syntax instead of explaining domain intent.
Broad exception swallowing, hidden defaults, or fallback behavior that masks missing data.
Changing public behavior without focused regression tests.

Optional references

reference.md - detailed guidance, examples, and templates.
testing.md - pytest patterns.
fastapi.md, flask.md, django.md - framework guidance.