Original Reddit post

Ok so I’ve been down the rabbit hole for way too long on this and I need actual people who’ve figured this out to just tell me what works. Basic setup: I run a small agency selling websites to local businesses. Claude handles like 80% of the actual build work, I close the clients and handle the relationship side. It’s been working but I know I’m leaving a lot on the table in terms of efficiency and quality. My current process is pretty simple — I create a project in Claude for each client, drop in a claude.md , a site_specs file and a site_facts file (basically research I’ve done on the business), and let it cook. Honestly it already does a lot. But here’s my problem: I keep running into the same cycle. Basic code errors, obvious visual stuff that I have to manually point out every single time like Claude just… doesn’t catch it even when I have error-checking instructions baked in. I fix one thing, something else breaks or it’s just a band-aid. It feels like no matter how much I try to tighten things up, there’s always friction. I’ve watched probably too many YouTube videos and read way too many posts but I always end up more confused than when I started because everyone’s workflow looks different and half the advice is vague as hell. So what I actually want to know is:

  • What specific skills, prompting patterns, or workflow structures have genuinely helped you get more consistent, higher quality output?
  • Is there something I’m missing in how I structure my project files that would reduce these recurring errors?
  • Any particular review/QA step you’ve built in that actually catches stuff before you have to? Not looking for “just use a better prompt lol” answers. Looking for people who’ve actually solved this at a process level. What’s working for you? submitted by /u/NullF4iTH

Originally posted by u/NullF4iTH on r/ClaudeCode