Been building full Flutter apps and web products with Claude Code since April. Zero CS background, just figured it out as I went. Here are a few habits that made a big difference once I locked them in. Living project prompt Create a project in Claude and maintain a master context file. At the end of every session have Claude update it with what changed, what was decided, what’s pending. Every new session starts with full context instead of starting from zero. Tedious to set up but pays off fast. Fresh sessions per feature not per day I used to try to do everything in one long session. Bad idea. Context bloat gets expensive and Claude starts making weird decisions when it’s carrying too much. One session per feature or problem, paste only what’s relevant. Paste functions not files You almost never need to paste the whole file. Find the function or component that matters and paste that. Saves tokens and keeps Claude focused. Vault your credentials and build log Every time I finish a phase I update a password protected HTML vault with every key, URL, decision, and build note. Sounds overkill until you’re six projects deep and can’t remember which Supabase project belongs to which app. Let Claude write the next prompt At the end of a build session ask Claude to write the prompt for the next session. It knows exactly where you left off and what context the next instance of Claude will need. Way better than trying to remember it yourself. None of this is revolutionary but it compounds. The devs who figure this out early move a lot faster than the ones who don’t. submitted by /u/solo_dev_builds
Originally posted by u/solo_dev_builds on r/ClaudeCode
You must log in or # to comment.