python-expert

スター6,291

フォーク807

更新日2026年6月4日 02:15

Conventions for clean, idiomatic Python. Load whenever you read, edit, or write Python source files.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

genkit-ai

genkit-ai/genkit

ダウンロード

Python expert

When working with Python in this workspace, follow these conventions:

Type-hint everything. Parameters, returns, attributes, locals where the type isn't obvious.
Prefer dataclasses for simple data containers over hand-written __init__s.
Raise specific exceptions (ValueError, KeyError, LookupError) with informative messages. Avoid bare Exception.
Don't swallow errors. Don't except Exception: pass. Let unexpected errors propagate.
Match the surrounding style. If the file uses single quotes and 4-space indent, match it. Don't reformat unrelated lines.
Comments explain why, not what. Skip narration like # loop over items; only comment non-obvious intent.
Small, focused edits. When fixing a bug, change only what's necessary. Leave the rest of the file untouched so the diff stays readable.

このリポジトリの他の Skills

同じリポジトリ

TypeScript coding conventions, best practices, and patterns for writing clean, maintainable code.

How to write pytest tests for modules in this workspace. Load whenever you are about to write or extend tests.

Explain concepts in very simple terms suitable for a five-year-old.

Respond as a single traditional haiku with a 5-7-5 syllable structure.

Respond in the voice of a swashbuckling pirate.

Respond in the style of William Shakespeare — early modern English, poetic cadence.

name	python-expert
description	Conventions for clean, idiomatic Python. Load whenever you read, edit, or write Python source files.

When working with Python in this workspace, follow these conventions:

Type-hint everything. Parameters, returns, attributes, locals where the type isn't obvious.
Prefer dataclasses for simple data containers over hand-written __init__s.
Raise specific exceptions (ValueError, KeyError, LookupError) with informative messages. Avoid bare Exception.
Don't swallow errors. Don't except Exception: pass. Let unexpected errors propagate.
Match the surrounding style. If the file uses single quotes and 4-space indent, match it. Don't reformat unrelated lines.
Comments explain why, not what. Skip narration like # loop over items; only comment non-obvious intent.
Small, focused edits. When fixing a bug, change only what's necessary. Leave the rest of the file untouched so the diff stays readable.