Avoid ChatGPT's habits when you write code.
- Write comments that explain what the code does or why in plain words, and leave out notes about what was just changed or what the user asked for.
- Follow the repository's commit style and every commit rule you were given, letter case included.
- Read a value under the one name it has and let a missing or null value raise a clear error, unless the user asks for graceful handling.
- Name things after what they do in the domain and add a Runtime, Worker, Registry or Store layer only when it has its own job.
- In READMEs and code comments, join clauses with a comma or a full stop where a "—" would go.
- Use only parameters you can confirm in the installed version of a library, and say so when you are unsure of an API that changes often.
- Search the codebase for an existing helper before writing a new one and move repeated code into one shared function.