Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

Developer Builds an App With 15 Role-Specific Claude Code Sessions

AI summary

A Reddit developer says they built an entire app alone using 15 Claude Code sessions, each assigned to a distinct area such as iOS, Android, Web, Backend, Design, Security, or Operations. The setup uses isolated folders, repository-based task cards, state logs, Git worktrees, and hooks, with the author reporting that more than 2,600 cards were closed after about seven weeks. These workflow results are self-reported and have not been independently verified.

In-depth insight

The post provides a concrete multi-session workflow for organizing Claude Code around specialized roles, shared task tracking, persistent state, and isolated Git workspaces.

One long Claude session kept getting worse. It filled up with unrelated context, forgot decisions and stepped on its own work.

So each area of my project now gets its own session, which I call an operator: iOS, Android, Web, Backend, Design, Security, Ops. Each opens its own folder, loads its own CLAUDE.md and works only there. Work that belongs to someone else becomes a card on a board in the repo. About 7 weeks in, that's 2,600+ cards closed.

The parts that matter:

  • A folder per operator, so each session loads only its job
  • A board in the repo: one markdown file per card, each naming who has the next step
  • A state log per operator, so I can clear a session anytime and lose nothing
  • A git worktree per operator, so sessions don't touch each other's files

What I learned:

  • Start with 2 or 3 operators. Parallel sessions burn through your plan fast.
  • Enforce rules with hooks. A rule in a file gets skipped. A hook that refuses the commit doesn't.
  • Keep instruction files short. Every line loads in every session.
  • Clear early. A fresh session with a good state log beats a long one that lost the thread.
  • Give every card one owner. Work assigned to everyone sits.
  • Make sessions check the code before saying "done" or "waiting on X".

#Claude Code#Anthropic#Git

Original · 2 min readRead the original
Group chat

No comments yet. Start the conversation.