My Claude Code and Antigravity Workflow for Running 3 Projects at Once

Running three active development projects simultaneously is not a productivity trick. It is a context management problem.

Code does not context-switch cleanly. When you set down a project at 3pm and pick it up at 10am the next morning, you lose: the current mental model of the codebase, the open questions from the previous session, the half-finished reasoning about a tricky bug, the plan for what to build next.

Claude Code and Antigravity solve different parts of this problem. Here is how I use them together.

What Claude Code Does

Claude Code is a terminal-native AI coding tool. You interact with it in the project directory. It can read files, write files, run commands, and understand the full codebase context — not just the file you have open.

For multi-project work, the key capability is: give Claude Code a task with enough context, and it will execute the task across multiple files without you manually tracking which file does what. "Add a reading_time_minutes field to the blog post type, update the database query to include it, and display it in the post header" is one prompt, not six manual edits.

This compresses the time from intent to implementation. It does not eliminate the need to understand the code — you still review every change — but it eliminates the time spent locating files, writing boilerplate, and managing the sequence of small edits.

What Antigravity Does

Antigravity is an IDE-level tool that preserves project context across sessions. The specific capability that matters: when you switch from Project A to Project B and then back to Project A, Antigravity restores the state you were in — open files, cursor positions, terminal sessions, and (critically for Claude Code) the conversation context from the previous session.

Without this, every session restart means re-explaining what you were working on. With it, you pick up mid-thought.

The Daily Structure

The workflow is structured around hard time blocks, not task completion:

Morning block (2 hours): Project A only. First thing in the morning, your context is fresh but generic — you have not loaded any project-specific state yet. Use this window for the project that needs the most focus or has the highest priority today.

Midday block (2 hours): Project B. After a break (or a meeting), load Project B. Antigravity restores the previous state. Review what was open, check the last Claude Code conversation, pick up the task.

Afternoon block (2 hours): Project C or continuation. Either the third project or a second session on whichever of the first two needs it more.

End-of-day ritual (15 minutes): Before closing everything, write a one-paragraph note in a scratch file for each active project: what you were doing, what the next step is, what the open questions are. This is the context that Claude Code reads at the start of the next session.

The Claude Code Skill Files

Skill files are custom instruction sets for Claude Code that live in the project directory. Each project has its own skill file that tells Claude Code: the tech stack, the naming conventions, the patterns used in this specific codebase, and the things to never do.

This matters for multi-project work because the patterns differ across projects. The gaming platform backend has a different error handling style than santoshpaudel.me. The news site has different component conventions than agenticai01.tech. Skill files prevent Claude Code from applying conventions from one project to another.

What Still Requires Manual Focus

Debugging is still manual work. Claude Code can help identify likely causes, but walking through a subtle bug — one that only manifests under specific data conditions — requires human attention that cannot be parallelized across projects.

Architecture decisions are single-session work. Deciding how to structure the wallet system, or whether to split agenticai01.tech into three subdomains versus one — these decisions need an uninterrupted block, not a shared hour.

The workflow does not turn three projects into three times the output. It turns three projects into roughly two times the output with better context preservation than unstructured multitasking.

---

Resources

• —Claude Code documentation — the terminal-based AI coding tool; how to install and configure it for a new project
• —Claude Code skill files — how to write and store skill files that encode per-project conventions

Related Posts

• —Running 3 Projects at Once: My Multitasking System With Claude Code — the broader daily structure the Claude Code workflow fits into
• —Skill Files Explained: How I Customized Claude Code for My Own Projects — the skill files that give Claude Code project-specific context at session start
• —Commit, Push, Deploy — All From One Prompt — the end-of-session deployment step that completes the workflow

---

Want to see what this workflow can build for you? I use Claude Code and this exact system on every client project. See my services or get in touch to talk about what you are building.