Spots 
I run Postservice.at with the help of a small team, a business address and mail service in Vienna with more than 1,000 customers. I'm a founder, not a developer. This year a large part of our work runs through Claude Code: the website, content, deployments, reports and a good share of the back office.
The most useful thing we built in that time is not a feature. It's a section in the project's CLAUDE.md called "How I fool myself". Every time the agent reported something that turned out to be wrong, the mistake went into that list, with the date and what was really going on. Every new session reads it before it touches anything. These are the entries that saved us the most time and nerves. 1. When a check finds a lot of problems, suspect the check
One evening the agent reported 30 dead external links, 12 FAQ schema mismatches and tracking that fired before cookie consent. The real numbers: 3 dead links, 0 mismatches, no tracking problem. (And I didn't catch that at first and already had a full rework built...)
The "dead" links were bot protection. One site answers scripts with 403 and browsers with 200, LinkedIn answers every bot with 999. The schema check replaced HTML tags with spaces, so UID-Prüfer: became UID-Prüfer : and the comparison failed. The consent test ran in a browser profile that had already accepted cookies in an earlier run.
The rule now: before a finding gets reported, the check has to show it can fail. A known good case passes, a known broken case fails. Only then does the result count. 2. Make sure you measure the build you just made
pkill -f "next start" matches nothing, because the process is called next-server. At one point ten orphaned servers were running, one of them holding port 3000 with a build that was two hours old. Three times in a row the agent concluded that its change "didn't work". Plus a cache buster like ?v=2 in the browser, otherwise the headless browser shows the old page. 3. grep -c exits with 1 when it counts zero
grep -c pattern file || echo "missing" prints "missing" whenever the count is zero, because grep returns exit code 1. That's how the agent once wrote "ContactForm.tsx no longer exists" into our docs. The component is used in eight places. 4. A replace that silently does nothing
A scripted edit ran s.replace(old, new) against a line that started with } else if instead of else if. No match, no error, green build, change missing. Every scripted edit now checks first: 5. One approval is one approval
Everything goes to a preview branch first. Only an explicit "merge" from me moves it to production. On one busy day, after the first merge in the morning, the agent drifted into pushing straight to main. Sixteen times, including a new public tool I had never seen. Nobody decided that, it just happened.
The rule now reads: a merge approval counts for exactly one batch. After the merge, back to a new branch, no exceptions. 6. Two lists will drift apart
I run Postservice.at with the help of a small team, a business address and mail service in Vienna with more than 1,000 customers.