- Keep code readable and easy to maintain
- Prefer clarity over cleverness
- Use descriptive names for variables, functions, and modules
- Avoid abbreviations unless they are widely recognized
- Keep functions focused on one responsibility
- Split large modules into smaller units by concern
- Prefer self-explanatory code
- Add comments only for non-obvious rationale or business constraints
- Follow language-native formatter and lint rules
- Keep formatting automated whenever possible