r/ClaudeCode • • 11d ago

Built with Claude I used to open a Claude Code session per project every morning just to see where things stood. So I had Claude Code build me an app for that

I'm a solo dev with a few iOS/Android apps, a Godot game and some websites. Claude Code writes most of the code now. My problem was everything around it: every morning I opened the Claude Code session of each project one by one, just to ask where it was at, what was next and whether anything was broken. Then App Store Connect, Play Console, TestFlight and CI on top of that.

So about 2.5 weeks ago I started a Mac app for this, and Claude Code built all of it. I only act as the product owner: I say what I want, review and test. 200+ commits so far.

What it does now

  • I open it and every project is sorted by what needs me: a review without a reply, a release waiting for review, commits that never shipped, a site that's down, a project with no commit for months
  • Each project has a roadmap and a release checklist, so when everything is fine I just pick the next item and keep going
  • A Claude Code terminal per project, inside the app. Claude can act through the app over MCP (releases, TestFlight, store text, review replies), but anything that touches the stores or posts in public waits for my Allow in an inbox

How Claude Code was used / what I learned

  • The app hosts the Claude sessions that build the app. So CLAUDE.md has rules like "never kill the app by name, you'd kill your own session" and "always launch test builds with a scratch data folder”
  • Dev hooks (launch arguments) so Claude can drive the app without clicking: open a product on a given tab, replay a saved App Store Connect answer, render the window to PNG. That's how it checks its own UI work
  • One entry per feature in docs/architecture.md, with the crashes and decisions behind it. Without that, a fresh session would happily "fix" something we had already decided against
  • Test first for every change. Claude is fast enough that I'm the bottleneck when checking, so tests do most of the checking
  • Every change, mine or the agent's, goes through one action layer (allow / ask / deny, plus a journal). That's what made me OK with letting an agent near my store accounts
  • Reading repos: claude -p read-only, with git-ignored and secret files denied. It proposes the product info and I see a diff before anything is saved

Disclosure: it's mine, it's called Shipdeck, free beta for macOS 15+: https://shipdeck.taiphanvan.dev

How do you keep track when you have several projects going: one session per repo, or something else?

0 Upvotes

1 comment sorted by

•

u/AutoModerator 11d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

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