code-stylelisted

# House code style Apply these while writing, not afterwards. A cleanup pass that strips comments from code written to be commented produces worse code than code written to need none. If a file already establishes a conflicting per-line convention, match the file and say so in your reply rather than silently mixing styles. ## 1. No comments Naming and types carry the meaning. When a line needs explaining, rename the thing or restructure the code until it does not. Do not write: - JSDoc or doc blocks on functions, interfaces, types, fields, or schemas - "why" narration or rationale - restatements of what the code does - section labels or banner dividers - TODO or FIXME prose Do not annotate defensive code to justify it. A timeout, a retry, an ordering constraint: if the reason matters, put it in the reply to the user, not in the file. ### The three exceptions **Schema metadata.** Zod `.describe()` calls and validation messages are values the program reads, not comments. Use them freely. ```ts const CreateUser = z.object({ email: z.string().email("Enter a valid email address"), role: z.enum(["admin", "member"]).describe("Determines dashboard access"), }) ``` **Region markers in hook files.** Use `//#region` and `//#endregion` to separate mutations from queries. Only in hook files, only for that split. See `frontend-standards` for the shape. **Genuinely inexpressible facts.** A workaround for a bug in an external dependency, or a line that will read as a mistake