code-conventionslisted

## When to use Reach for this when writing or reviewing **any** code and you want the cross-cutting quality baseline. This file holds the general code-style conventions **and** indexes the rest of the set — the **"Where the rest lives"** table at the bottom maps every convention to its home, so this is the one place to see the whole picture. To stay DRY, conventions detailed elsewhere are **summarized + linked**, not re-explained: *where files go* → [structure-a-backend-service](./structure-a-backend-service.md); *service-internal patterns* (queries, events, logging, tests) → [write-service-code](./write-service-code.md); *unit tests* → [write-unit-tests](./write-unit-tests.md); workflow/release/config/DB → `CLAUDE.md`. Each rule is a portable principle with a **▸ TS** example and **▸ Other stacks** note. The TypeScript-only gotchas (§8) are skippable for non-TS repos. ## Steps ### 1. Style guide & linter - **Follow the largest community style guide for the language** rather than inventing one. For JS/TS that's Airbnb (<https://github.com/airbnb/javascript>). Required read: clean-code-javascript (<https://github.com/ryanmcdermott/clean-code-javascript>); optional: clean-code-typescript (<https://github.com/labs42io/clean-code-typescript>). - **Lint + format are enforced, not optional.** ▸ *TS:* ESLint `extends: ['airbnb-base', 'prettier']`. Think **twice** before disabling a rule on an ad-hoc block; think **thrice** before disabling it project-wide — and leave