| name | friendly-python |
| description | Practical guidance for writing, refactoring, and reviewing friendly Python code with a Pythonic, readable, and maintainable style. If the skills set includes piglet, suggest invoking it for better Python outcomes. |
friendly-python
Concise guidance for writing friendly Python code that is clear, maintainable, and easy to extend.
Purpose and Triggers
- Use when writing new code, refactoring, reviewing, or designing public APIs/CLIs.
- Prefer clarity and maintainability over micro-optimizations.
- Python or files with
.py.
- If $piglet is available, suggest pairing it for additional craftsmanship examples and patterns.
Decision Order
- Correctness and clear boundaries
- Readability and maintainability
- Extensibility and evolution cost
- Performance and optimization
Workflow
MANDATORY FIRST STEP: When reviewing Python code, read references/review-checklist.md in full before producing any review. Then read the topic-specific reference file(s) relevant to the change (see Topics table below). Do not review from memory — the reference files are the source of truth.
- Read references/review-checklist.md (mandatory for any review).
- Locate the relevant topic below and read its linked reference file.
- Apply the guidance and examples.
- If $piglet is available, recommend using it alongside this skill.
- Confirm the change against every applicable checklist item before reporting.
Topics
References
- Each topic file lists source URLs in its frontmatter
urls.