/ia-python-services
Python patterns for CLI tools, async concurrency, and backend services. Use when working with Python code, building CLI apps, FastAPI services, async with asyncio, background jobs, or configuring uv, ruff, ty, pytest, or pyproject.toml.
Claude Code
$ npx -y skills add iliaal/whetstone --skill ia-python-services --agent claude-code
Codex
$ npx skills add iliaal/whetstone --skill ia-python-services -a codex -y
Cursor
$ npx skills add iliaal/whetstone --skill ia-python-services -a cursor -y
Gemini CLI
$ npx skills add iliaal/whetstone --skill ia-python-services -a gemini-cli -y
GitHub Copilot
$ npx skills add iliaal/whetstone --skill ia-python-services -a github-copilot -y
OpenCode
$ npx skills add iliaal/whetstone --skill ia-python-services -a opencode -y
Windsurf
$ npx skills add iliaal/whetstone --skill ia-python-services -a windsurf -y
SKILL.md
ia-python-services.SKILL.mdname: ia-python-services
class: language
description: >-
Python patterns for CLI tools, async concurrency, and backend services. Use
when working with Python code, building CLI apps, FastAPI services,
async with asyncio, background jobs, or configuring uv, ruff, ty, pytest, or
pyproject.toml.
paths:
- "**/*.py"
- "**/pyproject.toml"
- "**/ruff.toml"
- "**/uv.lock"
Python Services & CLI
Working rules
- Validate external inputs and responses at boundaries; preserve exception causes.
- **Keep missing results distinct from empty results.** When an empty collection means success, require the response field instead of defaulting it to empty; an all-default model can validate `{}` as success. Test missing, misspelled, explicitly empty, and populated payloads through the real validation boundary.
- Keep simple sequential work synchronous. Bound concurrent work, preserve cancellation, and keep task references.
- Give network calls timeouts; retry only failures and operations whose semantics permit it.
- Enforce job idempotency with atomic writes and database constraints.
- Preserve published API behavior and shared migration history.
- Match telemetry to an operational question and verify its output.
Discipline
- Simplicity first: every change as simple as possible, impact minimal code
- Only touch what's necessary; avoid introducing unrelated changes
- No hacky workarounds: if a fix feels wrong, step back and implement the clean solution
- Before adding a new abstraction, verify it appears in 3+ places. If not, inline it.
- Verify: see Verify section below; pass all checks with zero warnings before declaring done
Verify
- `uv run pytest` passes with zero failures
- `uv run ruff check .` passes with zero warnings
- `uv run ty check .` passes with zero errors
- Coverage target: 80%+ (`uv run pytest --cov`; add `--cov-report=html` for a browsable report)
Task-specific references
Read the relevant reference before implementing or reviewing the matching behavior:
- For packaging, environment configuration, CLI setup, or pytest behavior: [tooling-and-tests.md](./references/tooling-and-tests.md).
- For asyncio, background jobs, retries, pooling, timeouts, or health checks: [concurrency-and-resilience.md](./references/concurrency-and-resilience.md).
- For APIs, validation, errors, migrations, logging, metrics, or traces: [service-boundaries.md](./references/service-boundaries.md).
Existing specialized references, when the corresponding topic applies:
- [cli-tools.md](./references/cli-tools.md).
- [fastapi.md](./references/fastapi.md).
Read more
name: ia-python-services class: language description: >- Python patterns for CLI tools, async concurrency, and backend services. Use when working with Python code, building CLI apps, FastAPI services, async with asyncio, background jobs, or configuring uv, ruff, ty, pytest, or pyproject.toml. paths: - "**/*.py" - "**/pyproject.toml" - "**/ruff.toml" - "**/uv.lock"
Python Services & CLI
Working rules
- Validate external inputs and responses at boundaries; preserve exception causes.
- **Keep missing results distinct from empty results.** When an empty collection means success, require the response field instead of defaulting it to empty; an all-default model can validate `{}` as success. Test missing, misspelled, explicitly empty, and populated payloads through the real validation boundary.
- Keep simple sequential work synchronous. Bound concurrent work, preserve cancellation, and keep task references.
- Give network calls timeouts; retry only failures and operations whose semantics permit it.
- Enforce job idempotency with atomic writes and database constraints.
- Preserve published API behavior and shared migration history.
- Match telemetry to an operational question and verify its output.
Discipline
- Simplicity first: every change as simple as possible, impact minimal code
- Only touch what's necessary; avoid introducing unrelated changes
- No hacky workarounds: if a fix feels wrong, step back and implement the clean solution
- Before adding a new abstraction, verify it appears in 3+ places. If not, inline it.
- Verify: see Verify section below; pass all checks with zero warnings before declaring done
Verify
- `uv run pytest` passes with zero failures
- `uv run ruff check .` passes with zero warnings
- `uv run ty check .` passes with zero errors
- Coverage target: 80%+ (`uv run pytest --cov`; add `--cov-report=html` for a browsable report)
Task-specific references
Read the relevant reference before implementing or reviewing the matching behavior:
- For packaging, environment configuration, CLI setup, or pytest behavior: [tooling-and-tests.md](./references/tooling-and-tests.md).
- For asyncio, background jobs, retries, pooling, timeouts, or health checks: [concurrency-and-resilience.md](./references/concurrency-and-resilience.md).
- For APIs, validation, errors, migrations, logging, metrics, or traces: [service-boundaries.md](./references/service-boundaries.md).
Existing specialized references, when the corresponding topic applies:
- [cli-tools.md](./references/cli-tools.md).
- [fastapi.md](./references/fastapi.md).
A Claude Code plugin that makes AI coding agents follow engineering discipline. Plan before coding. Verify before claiming done. Find root cause before patching. Review before merge. Skills activate based on file type and task signals, not manual toggling.
Other skills on whetstone.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about ia-python-services.
- Which coding agents can use ia-python-services?
- ia-python-services installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

