I’ve started wondering whether Claude Code’s idea of “done” is actually too narrow for real applications. It can build the feature, run the tests, fix the failures, and tell you everything is working. But there seems to be a gap between “the requested code change works” and “this application is actually ready for other people to use.” For example, after Claude Code finishes a feature, there are still questions like: Did it test the important permission edge cases, or just the happy path? Did it verify the actual deployed behavior? Are integrations handling failures and retries? Did the implementation introduce an unexpected third-party request? Is session replay or analytics configured safely? Are robots.txt, sitemap.xml, metadata, canonical URLs, etc. actually set up? Are there missing error states, empty states, pages, or other product details Claude simply wasn’t asked about? Are there privacy, compliance, or other things that should be reviewed before sharing the app? Most importantly, what did Claude assume without being explicitly told? That’s the part I find interesting with Claude Code: it can be extremely good at implementing what you asked for, while the harder problem is knowing what you forgot to ask for. Tests can tell you that the things you tested passed. They don’t necessarily tell you what you never thought to test. For people using Claude Code seriously, what’s your process after Claude says “done” before you actually put the app in front of users? submitted by /u/Glittering-Glass6135
Originally posted by u/Glittering-Glass6135 on r/ClaudeCode