python
Use when editing Python files, pyproject.toml, requirements.txt, setup.py, setup.cfg, uv workflows, ruff, mypy, typing, packaging, scripts, Cython, or Mypyc extension builds.
Best use case
python is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when editing Python files, pyproject.toml, requirements.txt, setup.py, setup.cfg, uv workflows, ruff, mypy, typing, packaging, scripts, Cython, or Mypyc extension builds.
Teams using python should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/python/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How python Compares
| Feature / Agent | python | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when editing Python files, pyproject.toml, requirements.txt, setup.py, setup.cfg, uv workflows, ruff, mypy, typing, packaging, scripts, Cython, or Mypyc extension builds.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Python Skill ## Overview Expert knowledge for Python development in this workspace. This skill aggregates tooling, build systems, and quality standards. ### Core Standards As per workspace rules, the following are **MANDATORY**: 1. **Tooling**: `uv` is the required tool for Python package and environment management. 2. **Execution**: Always run python programs with the `uv run` prefix. 3. **Installation**: Use `uv` with `pyproject.toml` and install to a virtual environment. 4. **Typing**: Use `>=3.10` types as per PEP 585 (e.g., `dict`, `list` instead of `typing.Dict`, `typing.List`). 5. **Comments**: Prefer docstrings and type annotations over inline comments. Use inline comments only when the logic is non-obvious and cannot be clarified through better naming or type hints. --- <workflow> ## References Index For detailed guides on specific tools and sub-systems, refer to the following documents: ### Package & Project Management - **[`uv` Guide](references/uv.md)** - Initializing projects, managing dependencies, workspaces, and tool execution (`uvx`). ### Code Quality - **[Quality Standards](references/quality.md)** - Ruff, Mypy, and Pyright configurations. ### Build Systems & compiled Extensions - **[Building & Packaging](references/build.md)** - Standalone binaries, patching, and distributing. - **[Cython Extensions](references/cython.md)** - Compiling C extensions for performance. - **[Mypyc Extensions](references/mypyc.md)** - Mypyc-compatible classes and compilation workflows. </workflow> <example> ## Example: pyproject.toml Setup ```toml [project] name = "myapp" version = "0.1.0" requires-python = ">=3.12" dependencies = ["litestar>=2.0", "sqlalchemy>=2.0"] [tool.uv] dev-dependencies = ["pytest>=8.0", "ruff>=0.8", "mypy>=1.13"] [tool.ruff] target-version = "py312" line-length = 120 [tool.ruff.lint] select = ["ALL"] ignore = ["D", "ANN101"] [tool.mypy] strict = true python_version = "3.12" ``` </example> --- ## Official References - <https://docs.astral.sh/uv/> - <https://docs.astral.sh/ruff/> - <https://mypy.readthedocs.io/> - <https://mypyc.readthedocs.io/> ## Shared Styleguide Baseline - Use shared styleguides for generic language/framework rules to reduce duplication in this skill. - [General Principles](https://github.com/cofin/flow/blob/main/templates/styleguides/general.md) - [Python](https://github.com/cofin/flow/blob/main/templates/styleguides/languages/python.md) - Keep this skill focused on tool-specific workflows, edge cases, and integration details. <guardrails> ## Guardrails Add guardrails instructions here. </guardrails> <validation> ## Validation Add validation instructions here. </validation>
Related Skills
flow-memory-keeper
Use at task, phase, flow, sync, archive, finish, revise, or failure checkpoints to keep Flow specs clean, capture learnings and failures, elevate durable patterns, and refine this skill with project-specific nuances
vue
Use when editing Vue projects, .vue files, vue.config.js, Vue 3 components, Composition API, <script setup>, SFC state, deployment workflows, or Vue CI configuration.
vite
Use when editing Vite projects, vite.config.ts, vite.config.js, Vite plugins, HMR, asset bundling, frontend build settings, deployment config, or Litestar/Vite integration.
uvicorn
Use when deploying ASGI apps with uvicorn, editing uvicorn CLI commands, Config or Server usage, workers, reload, event loop selection, SSL, lifespan, logging, or development server behavior.
tracer
Use when tracing execution paths, mapping dependencies, understanding unfamiliar code, following data flow, investigating end-to-end behavior, debugging call chains, or deciding which files to read next.
testing
Use when writing or refactoring tests, editing test_*.py, *.test.ts, *.spec.ts, conftest.py, vitest.config.ts, pytest fixtures, mocks, coverage, async tests, anyio, or test failure debugging.
terraform
Use when creating, adopting, refactoring, or operating Terraform, *.tf files, .terraform.lock.hcl, terragrunt.hcl, root modules, backends, state, workspaces, imports, CI plan/apply, tests, or policy checks.
tanstack
Use when editing TanStack code, @tanstack imports, useQuery, createRouter, React Query, TanStack Router, Table, Form, Store, file-based routing, data fetching, or SPA state management.
tailwind
Use when styling with Tailwind CSS, editing tailwind.config.ts, tailwind.config.js, @tailwind directives, utility classes, responsive layouts, @apply, cn(), @theme config, dark mode, or forms.
svelte
Use when editing Svelte components, .svelte files, svelte.config.js, Svelte 5 runes, $state, $derived, SvelteKit, component state, or migrating away from Svelte 4 patterns.
sqlserver
Use when writing T-SQL, editing SQL Server .sql files, using sqlcmd, SQL Server connection strings, stored procedures, execution plans, indexes, Always On, JSON, security, or connector code.
sqlalchemy
Use when editing SQLAlchemy code, sqlalchemy imports, mapped_column, DeclarativeBase, ORM models, relationships, select() queries, async sessions, engines, events, or migrations.