code-craftlisted

# Code craft A model writes what it has seen most, and what it has seen most is the average of every repository in its training data. That average has a shape: everything imports everything, nothing is ever deleted, every error is caught and swallowed, and every function that fits nowhere lands in `utils`. It compiles. It passes a glance. It costs someone six months later, when the file that was sixty lines is eight hundred and nobody can say what it is for. Craft is decisions made while writing. There is no cleanup pass that adds it afterwards. ## 1. Read the neighbours before you write On a codebase this team did not write, that means the whole project and not one file — and it is worth the extra care, because you are changing something other people depend on with tests you did not write. `davinci:brownfield` covers orienting, pinning current behaviour before changing it, and knowing the blast radius. The clearest tell of outside authorship is code that works and does not belong. Before the first line, read the two or three files nearest the change and take from them: - how errors are raised, wrapped, and handled here - how modules are named, and how deep the tree actually goes - how tests are written, and what they assert on - import ordering, naming, whether types are declared or inferred `.devteam/stack-profile.md` states the conventions someone wrote down; the neighbouring files carry the ones nobody did. Where the two disagree, the profile wins and you note the