Scaling Myself: How I Run 22 Claude Code Sessions for DS4 Migration
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
An iOS engineer at Mercari shares how they managed a large-scale design system migration (DS3 to DS4) by running 22 simultaneous Claude Code sessions. The setup relies on git worktrees for parallel branch checkouts without rebuilds, a shared Bazel output cache with a file-based lock protocol, and an Obsidian Vault symlinked to Claude Code's global config as a single source of truth for 35+ custom slash commands encoding the migration playbook. Key practices include dedicated 'brain' sessions for planning vs. execution sessions for coding, a /prune-branches command to handle squash-merge stale branch detection, stacked PR chain management via a single persistent Claude session, and a 'remove and build' verification technique that caught hidden DS3 dependencies in 3 of 21 migrated screens.
