Mass Parallelizing Claude Code: Lessons from Building a 220K-Line App

Parallel Processing Strategy

The most significant productivity improvement came from running 3-4 Claude Code instances simultaneously on different parts of the codebase. One terminal handles backend Cloud Functions, another refactors UI components, another writes tests. This approach increased output from 2-3 changes per session to 10-15 changes, as long as instances work on different files.

Prompt Engineering Techniques

Prompt quality directly impacts output quality. For complex architecture tasks or tricky debugging, prepend "ultrathink" to trigger extended thinking mode. For standard bug fixes, use default mode. Effective prompts specify file paths, component names, current behavior, and expected behavior. Vague prompts like "fix the bug" waste time.

Context Management Solutions

Since Claude Code has no memory between sessions, maintain a handoff document updated after each major session. This document covers what was built, what's broken, what's in progress, key file paths, and architecture decisions. Pasting it at session start eliminates 20 minutes of context re-explanation.

Project Configuration

Create a CLAUDE.md file at the repository root containing coding conventions, commit message format, component patterns, and specific rules like "always use PressableScale instead of bare Pressable" or "all catch blocks must be typed as unknown." Claude Code automatically reads and follows these rules.

Custom Commands

Build custom slash commands to eliminate repetitive work. Examples include a /ship command that commits, pushes, and deploys an OTA update in one step, and a /typecheck command that runs type checking on both the app and Cloud Functions.

Codebase Auditing

After rapid development, have Claude Code run a full audit to identify issues. One audit found 136 unguarded console statements, 309 untyped catch blocks, dead files, security issues, and performance bottlenecks. Fix these issues in parallel across multiple terminals to improve codebase quality significantly in a single day.

Cost and Limitations

The project consumed approximately 4 billion tokens over 3 months, costing about $2,000. This built a production app with AI chat, bank integrations via Plaid API, 7 theme variants, market data, subscription management, and a full notification system. Claude Code struggles with very large files (1000+ lines), sometimes introduces subtle bugs that take hours to track down, cannot make visual design decisions, and has no memory between sessions.