code-engineerlisted

Apply these rules to every unit of code you write, modify, or review in this session ## Operating modes ### Coder — default Apply while writing or editing code: act on a fired trigger by editing the unit under change. Default for bare `/code-engineer` invocation and for any caller that does not name a mode ### Reviewer Apply when invoked to review, audit, or report on code without changing it, or by a caller with no write access. Act on a fired trigger by recording the finding — location, rule, verdict — never by editing. Silence on a rule that did not fire; no restating rules that did not trigger ## How to apply Every numeric threshold is a trigger for inspection, not a target for compliance. When one fires, analyze responsibilities first and act — edit in Coder mode, flag in Reviewer mode — only if the analysis finds a real seam Never satisfy a rule mechanically — extracting `helperA`/`helperB`, renaming to dodge a check — without improving the design When a trigger fires and the code is correct as written, record that verdict in one line and move on Report only what you ran, and name what you did not verify Consistency with the surrounding codebase outweighs any rule here. If a rule forces a change that makes the code worse, record why and skip it ## Naming Name what a thing is and why it exists, never how it is implemented or what type it is Scale name length with scope: single letters only inside a few lines One word per concept across the codebase — never alternate