python-expert

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

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

npx skills add https://github.com/genkit-ai/genkit --skill python-expert

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

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.

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.

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.