Like so many, I find that claude is attracted to shiny objects and when it finds an issue, often legit, it tends to build process or guidelines around prevention of that issue in the future - then becomes obsessed with it. I know I’m not the only one who suffers watching Claude get in it’s own way. So, I have been working to find ways to keep Claude in a practical state of forward motion without ignoring the sometimes-critical issues it avoids. I am relatively new at this so forgive me if this is 101 stuff, but the two things I found that work well are:
- no changes to md files, ever, without my approval, and they have to be filed as a ticket/issue for later review
- I found that the phrase “avoid allowing a check that caught the previous incident to become a permanent universal ritual.” seems to have done the trick. Instead of saying “I found an issue, I’ll be sure to check for this issue for the rest of eternity and won’t shut up about it” it says: “I found an issue. This should have been caught by process ____, which could be improved to avoid this in the future. Should I open an issue to consider making a change to future process?” Or sometimes, it just fixes the issue. Sometimes finding an issue is just… finding an issue. I’m curious how everyone else keeps Claude moving forward and not getting sidetracked? submitted by /u/Helpful_Bandicoot383
Originally posted by u/Helpful_Bandicoot383 on r/ClaudeCode
You must log in or # to comment.