I Was Spending $200/Month on AI Tokens Just Setting Up Projects. Here's How I Cut It by 80%.
Every time I started a new Flutter project, the conversation with Claude looked the same:
"Set up a Flutter project with clean architecture, Riverpod, GoRouter..."
Then 15 back-and-forth messages later, I'd have a mediocre folder structure that I'd spend the next 2 hours fixing. That's roughly 8,000-12,000 tokens per project — just on setup.
Multiply that by the 3-4 projects I start every month (client work, side projects, experiments), and I was burning $150-200/month before writing a single line of business logic.
The real problem
AI tools are incredible at building features. They're terrible at architecture. Every time you start fresh, Claude or Cursor has zero context about your project. It guesses at folder structure. It picks random state management approaches. It creates inconsistent patterns across files.
You end up spending more tokens fixing the AI's setup than you would have spent doing it manually.
What actually works
The fix isn't better prompts. It's not giving the AI a 2,000 word system prompt explaining your architecture. It's starting with code the AI already understands.
When your project includes a CLAUDE.md file that documents every service, every provider, every pattern — the AI stops guessing. It reads the guide, understands the architecture, and writes code that fits perfectly on the first try.
Here's the difference in token usage I measured across 10 projects:
**Without project guide:** 8,000-12,000 tokens per feature **With project guide:** 1,500-3,000 tokens per feature
That's a 75% reduction. Not because the AI got smarter, but because it stopped wasting tokens asking "what state management do you use?" and "where should I put this file?"
The setup problem is solved
Tools like Shipeed generate the project AND the AI guide files in one command. You run `shipeed init`, pick your framework and integrations, and get a production-ready project where every AI tool (Claude, Cursor, Copilot, Windsurf) already knows the codebase.
The boilerplate conversation is over. You open the project and say "add a profile page" and the AI nails it first try — because it read the guide.
If you're still spending the first hour of every project on folder structure and config files, you're burning tokens on a solved problem.