I have noticed it generating good code even in domains I'm an expert in! I think that it is extremely tempting to just let Claude run freely over the codebase

I have noticed it generating good code even in domains I'm an expert in! I think that it is extremely tempting to just let Claude run freely over the codebase and turn it into unmaintainable slop. My hot take is that this is fine. It doesn't take very long to come up with a list of simple yes-or-no style rules (e.g. modules should be descoped to simple files, each module must have tests at filename_test, a reasonable reader should find comments to be concise and not extraneous, etc). It doesn't take very long to set up a precommit hook that starts a short Claude session to check each rule, block if any are failed, and explain the issues. After that? I've found that it's pretty easy to get good code written, and even easier to maintain it. Obviously anything with a value judgement is an avenue for issues, but even a non-frontier model can generally do a passable job answering questions. As long as you eventually read the code to decide on big-picture refactorings, you'll be in a great place.