Session Management

Session Management

Claude Code has no memory between sessions. Every new session starts blank and reads your CLAUDE.md. This skill ensures continuity.

Context Window Management

Claude Code's context window is large but finite. Everything loaded into it competes for attention. Overload it and quality drops.

The 500-Line Rule

Your CLAUDE.md should stay under 500 lines. This is the file loaded into every session. If it's too long, Claude Code starts ignoring rules at the bottom.

What belongs in CLAUDE.md (always loaded):

• Core principles (native SwiftUI, iOS version, HIG)
• Navigation structure
• Architecture conventions
• Custom components list
• What NOT to do
• Known gotchas
• Build configuration
• .pbxproj safety rule

What belongs in separate files (loaded when needed):

• App spec (APP_SPEC.md)
• Design system (DESIGN_SYSTEM.md)
• Detailed component specs
• Reference documentation

Per-Session Context Loading

At the start of each session, tell Claude Code what to focus on:

Read CLAUDE.md. Today we're working on the Settings flow.
Also read the Settings section of APP_SPEC.md. Ignore other
sections for now.

This focuses the context on what matters for THIS session rather than loading everything.

Signs of Context Overload

• Claude Code starts ignoring rules from your CLAUDE.md
• It builds custom components when native ones exist
• It forgets the architecture pattern mid-session
• Responses get slower or less precise
• It repeats mistakes you've already corrected

Fix: Start a new session. Load only the CLAUDE.md and the specific section you're working on. Keep the scope narrow.

Session Continuity

The Problem

Claude Code sessions don't survive Mac restarts, long periods of inactivity, or network timeouts. When a session ends, all conversation context is lost. The code on disk is fine (it's committed to git), but Claude Code doesn't know what it was doing.

The Solution: Git as Your Checkpoint System

Your git history IS your session memory. Every commit message tells the next session what happened.

End of every work session:

Commit all changes with a descriptive message that includes
what's done and what's next. Example:
"Settings main screen complete. Next: build notification
preferences sub-page."

Start of the next session:

Read CLAUDE.md. Check the git log for recent commits to
understand what's been done. We're continuing from where
the last session left off. The most recent commit message
describes what to do next.

The Session Handoff Pattern

Before you close your laptop or end a session, tell Claude Code:

Write a brief session summary as a comment at the top of
CLAUDE.md under a "## Current Status" section. Include:
- What screens are complete
- What screen is in progress
- What's next
- Any unresolved issues

The next session reads this and picks up exactly where you left off. Update this section at the end of every session.

Example Current Status Section

## Current Status (Updated 2026-04-07)
- DONE: Scaffolding, Projects Home, New Project Sheet, Settings Main
- IN PROGRESS: Project Detail (stitch counter custom component)
- NEXT: Explore tab, Onboarding
- ISSUES: Liquid Glass on nav bar flickers during sheet dismiss (logged as gotcha)

Conductor Session Management

Each Conductor workspace is an independent session. When managing multiple:

Naming Convention

Name workspaces after their task, not generic labels:

• "build-project-detail" not "workspace-3"
• "fix-navigation-bug" not "hotfix"
• "polish-home-screen" not "updates"

Workspace Lifecycle

1. Create workspace with descriptive name
2. Give it a focused task (one screen, one feature, one bug)
3. Let it work (monitor via Remote Control if away)
4. Review the output
5. Merge or request changes
6. Close the workspace

Don't keep stale workspaces open. Merge or close within 24 hours. Long-lived branches diverge from main and create painful merges.

Recovering After Conversation Compaction

Long sessions hit Claude Code's context limit and trigger automatic compaction — the harness summarizes earlier messages and replaces them with a digest, freeing space for new work. Compaction preserves the gist of the session but loses precise file content, exact diffs, and any in-context state that wasn't on disk.

The danger zone is the first turn after compaction: the agent may "remember" file contents that have since changed, or assume an active branch that has since merged. Without a recovery ritual, the next edit can land on stale assumptions and produce a regression that's hard to attribute.

The Post-Compaction Ground Check

Run this before any edit in the first turn after compaction (or whenever the conversation feels like it's been summarized):

# 1. What branch am I on, and what's the state?
git status
git log --oneline -10

# 2. Is the repo clean, or are there uncommitted changes from before
#    compaction that the digest may have lost track of?
git diff
git diff --staged

# 3. Has the upstream moved while I was working?
git fetch origin
git log --oneline HEAD..origin/main

If any of those reveal surprises — uncommitted changes that weren't in the digest, an upstream that's moved, a branch that was merged — STOP and reconcile before editing. The cost of reconciling is minutes; the cost of overwriting an unfamiliar change is hours.

Re-Reading CLAUDE.md After Compaction

The compaction digest may have summarized your CLAUDE.md content. Before relying on any rule, re-read the actual file:

Read CLAUDE.md and the active plan file (if any) before making
the next edit. Do not trust your in-context summary of either.

This re-establishes ground truth for project conventions, custom-component lists, known gotchas, and any active spec.

Re-Reading Files Before Editing

Compaction often summarizes file contents away. The cheapest insurance: re-read any file you're about to edit, even if you "remember" it. The Read tool is fast and the harness tracks what you've read against what you can edit.

When in doubt, the prompt:

Before editing <file>, read it again. The earlier conversation
may have been compacted and the in-context content may be stale.

Signals Compaction Just Happened

Watch for these in the first turn back:

• The system note announcing compaction (explicit signal)
• A "Summary:" header in the most recent system message
• File-content references that feel sparse compared to the original
• The session-start timestamp older than the timestamp on a recent commit

When you see any of these, run the ground check before editing.

Resuming From Your Phone

If a Remote Control session times out:

1. Your Mac needs to be awake with Claude Code running
2. Start a new Remote Control session from the same workspace
3. The git state is preserved even if the conversation is lost
4. Tell Claude Code to read CLAUDE.md and check git log for context

If your Mac went to sleep:

1. You can't reconnect until someone (or a scheduled task) wakes it
2. Consider: macOS Energy Saver settings to prevent sleep when plugged in
3. Or use Dispatch to send a task that wakes the Mac

Anti-Patterns