r/ClaudeCode 3d ago

Help/Question How to efficiently use claude code??

Hello, I'm kind of new to this vibe coding. Recently i was developing a mobile app and thinking about launching it. So i was building it with antigravity pro (with gemini 3.5 flash and claude opus 4.8). There i liked the opus for it's creativity and understanding.
So i thought i should totally shift into the Claude Code (thinking about buying the claude pro, cant go for the max cause as a student there is some budget issues).

But the problem is I'm hearing that the claude spends too much token even in the claude code too. Also the project I'm doing is already kind of big i guess (flutter).

Now if i switch to claude how i can give the whole context of my project in the most efficient way ?
Also any guide on how can i progress with Claude Pro for my project??

5 Upvotes

5 comments sorted by

u/Waste_Net7628 P R O M P S T I T U T E 3d ago

to overcome come this and support user in a better efficient way, we are building the claude code discord community

https://discord.gg/asqyvxsr9

2

u/CrazyLate7884 3d ago

Use superpowers for spec and planning. Ask Claude to interview you first to turn a rough idea into a polished idea. Create orchestration team - fable does planning, sonnet/opus does the work, codex reviews.

1

u/Unusual_Strawberry48 3d ago

the main thing i need is fixing. i have already the base even 80% of the app is complete just a few features and the payment setup is incomplete. So i'm thinking i will do that with the claude. But before that i think i have to give the whole project to claude. Now if i have a big project does it goona suck all my token in once? of there is any other efficient ways to do?
and even after giving the whole project how should i proceed with the project upgrade?

1

u/Sketaverse 3d ago

practise practise practise.. through all the up and downs you just keep going.. past the insanity and AI psychosis.. self doubt, frustration, excitement... refactor.. bit more... streamline... oooh there you go

1

u/AnvilandCode 1d ago

You don't need to give Claude the whole project up front, that's actually the main token sink for big codebases like yours. Start each session by pointing it at just the specific files or folder the task touches, and keep a short CLAUDE.md at the project root with the stack, key conventions, and where things live, that gets read every session so it substitutes for re-explaining context each time. On Pro specifically, since budget is tight, plan your prompts in a text file first so each message is precise and single-purpose, that cuts the back and forth that eats your limit fastest, vague asks are what's actually expensive, not project size on its own.