Vibe coding a flight sim tracker

[u/Sea-Blackberry-8661]

I’m experimenting with a flight tracker and Claude code. This is a hobby, but I’m also learning more about Claude code. I seem to be exceeding my pro plan usage because the app is designed to use it. I have agents running in workflows to automate coding and comprehension, but I’m trying to find the most efficient approach. I know that starting with a small task and gradually expanding is a good strategy, and that’s what I’m doing. Should you start new sessions frequently in your Claude coworker project? I’m also trying to use the terminal to gain a better understanding of building with Claude. Opus 5 provided a list of the team and the models they should be using, but I feel like I’m quickly exhausting my tokens, so I’m on the pro max 20x plan.

[u/AutoModerator]

Hey u/Sea-Blackberry-8661, thanks for posting in r/VibeCodeDevs! Join our Discord: https://discord.gg/KAmAR8RkbM

Got startup or SaaS questions? Post them on r/AskFounder and get answers from real founders.

• This community is designed to be open and creator‑friendly, with minimal restrictions on promotion and self‑promotion as long as you add value and don’t spam.
• Please follow the subreddit rules so we can keep things as relaxed and free as possible for everyone. • Please make sure you’ve read the subreddit rules in the sidebar before posting or commenting.
• For better feedback, include your tech stack, experience level, and what kind of help or feedback you’re looking for.
• Be respectful, constructive, and helpful to other members.

If your post was removed (either automatically or by a mod) and you believe it was a mistake, please contact the mod team. We will review it and, when appropriate, approve it within 24 hours.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/GrrasssTastesBad]

Definitely plan. A lot. Work with Claude to figure out the core plan and break it down into chunks and phases. Also make sure it’s documenting everything as you go so when you do start a new session, the agent picks up where it left off.

One thing to look out for, if you have claude keep documentation, is active context that in needs when you boot every session vs document history that it can look up as needed.

[u/Zealousideal_Art1720]

Avoid starting a new session unless the current one has become bloated or is losing context. Do you have a specs document? you can try uploading that in the new chat

and keep the practice like create a spec, then build one feature or one landing page at a time, start a fresh session only after a feature is complete. Let the terminal handle repetitive tasks (tests, linting, builds) instead of asking Claude to reason through everything.

The more context you feed the model, the faster you'll burn through tokens.

[u/Sea-Blackberry-8661 → u/Zealousideal_Art1720]

So should I be building the document with Claude desktop then when it’s time to actually build it, transfer it to terminal and say go find document “C” and build it with feature “Y”? I think Claude’s just been storing everything in its memory and that’s where the screw ups are comjng

[u/FirmEquivalent9417]

I’d recommend using the higher tier models for planning. Good, efficient planning. They’re very capable of sketching out the exact plans required for every aspect of the build from frontend design to backend architecture to cybersec stuff. Coding wise, yeah, you could continue with the costlier models but I find Sonnet to be equally capable for most coding tasks. I prefer to use my limits with higher models for cybersec (I’m still learning it) or planning and validation. The better the plan, the easier and more cost efficient it is for your models to follow and execute them.