Architecting Python Changes

This skill is the first stop for non-trivial Python architecture decisions. It is both a compact guide and a router to deeper project docs and domain skills.

Default Approach

1. Classify the change:
   • small local fix
   • feature adding new behavior or a new caller
   • refactor moving responsibilities or dependencies
   • project setup or framework choice
2. Ask yourself what is actually expected to change later:
   • business rules
   • validation or transport
   • UI or API surface
   • infrastructure or third-party dependency