# Quality Guidelines

> Code quality standards for backend development.

---

## Overview

These guidelines document the project's backend coding rules. Keep logic readable, keep behavior obvious, and leave a short note only where future readers need one.

---

## Forbidden Patterns

- Do not write commentary on obviously named code
- Do not add long-winded explanatory comments that repeat the code
- Do not leave temporary comment noise around finished logic

---

## Required Patterns

### Commenting Critical Logic

When you touch key business branches, state transitions, boundary conditions, cross-module calls, or tricky algorithms, add a short comment that explains intent or why the branch exists.

- Keep the comment concise
- Explain why, not what
- Skip comments on self-evident lines

---

## Testing Requirements

- Re-run the relevant backend tests when comment-sensitive logic changes
- If the edit changes behavior, add or update a regression test

---

## Code Review Checklist

- Is the new comment only where readers actually need help?
- Does the comment explain intent instead of restating code?
- Did the logic change stay aligned with the surrounding backend conventions?