noticed a pattern after a few weeks of heavy claude code use. give it a feature and it’ll nail the main flow, clean code, sensible structure. but it almost never adds empty states, error handling, or loading feedback unless you explicitly spell it out in the prompt. and if you spell it out every time, your prompts balloon and you still forget half of them. what actually worked was writing the non-negotiables into a file claude reads on every task instead of re-typing them. stuff like “any network call gets a loading and error state” and “no orphan screens without a back action.” the difference in output quality was bigger than any clever prompt wording i tried. the lesson for me was that claude is great at execution but terrible at remembering your standards. so stop relying on memory and make the standards part of the context every single time. anyone else found a clean way to keep that file from going stale? submitted by /u/Wooden-Fee5787
Originally posted by u/Wooden-Fee5787 on r/ClaudeCode