📁
The council recommends
On: "Should a three-person startup use a monorepo or separate repos for web and mobile?"
Top pick
Start with a lightweight monorepo
Set up a single monorepo housing both web and mobile apps alongside shared packages for types, API clients, and domain logic. At your team size, the overhead of synchronizing separate repos, managing internal package releases, and fixing contract drift far outweighs repo-scale drawbacks. Keep tooling lightweight with Turborepo or pnpm workspaces rather than complex enterprise setups.
Runner-up
Separate repositories, justified only if mobile is written in native Swift/Kotlin with zero shared TypeScript logic.
Wildcard
A backend-inclusive monorepo that couples your API, web, and mobile contracts into fully atomic full-stack PRs.
Best time
Adopt this from day one, as splitting into separate repos later is far easier than merging drift-heavy codebases.
95%
aligned
Average confidence 87%
All experts unanimously recommend a lightweight monorepo to minimize coordination drag for a three-person team.
Your turnFacing a decision like this?Council puts 3 AI models on your question and gives you one verdict. Free, no signup.
Not on this panel
Kimi K3.1 and Claude Fable 5.1 didn't sit on this council.
Council Pro seats the strongest model from every lab.
Where they agree
✓A monorepo eliminates coordination friction and duplicate API contracts.
✓Shared packages for types, API clients, and validation save significant dev time.
✓Separate repositories impose unnecessary multi-repo CI and versioning overhead.
Where they diverge
↔Google warns against heavy tools like Nx, whereas Anthropic explicitly lists Nx as viable.
↔Anthropic notes mobile framework hurdles like Metro workspace config, unlike the others.
↔Google suggests Bun workspaces, whereas OpenAI and Anthropic focus on pnpm, Yarn, or Turborepo.
The 3 takes
GPT-5.6 TerraLens · Coordination & architecture
Use a monorepo with apps/web, apps/mobile, and shared packages to streamline single-PR cross-platform updates.
90% confident
Claude Sonnet 5.5Lens · Stack pragmatism & caveats
Adopt a single monorepo for atomic PRs, but configure Metro workspaces and CI caching carefully.
80% confident
Gemini 3.8 FlashLens · Simplicity & tool overhead
Choose a lightweight monorepo using Turborepo or Bun to share contracts without heavy enterprise tool bloat.
92% confident
InstinctJev · TypeSafeCostly to undoMostly facts
Instinct said separate repos for web and mobile (61%). The council chose monorepo instead.
Related sessions
Take the council with you
Ask, follow up and revisit every verdict from your phone.
Synthesized from 3 independent expert passes. Treat as informed input, not a guarantee. Your own judgment is the final vote.