# Python Guidance

- Prefer clear modules, typed interfaces where helpful, and explicit data validation.
- Keep framework conventions intact instead of introducing project-specific patterns casually.
- Test the changed behavior at the right level: function, service, API, or end-to-end flow.
- Record operational changes such as env vars, migrations, or deployment effects.
- Use documentation updates for durable contracts, not transient implementation commentary.