Pro Workflow

The Core Insight

"80% of my code is written by AI, 20% is spent reviewing and correcting it." — Karpathy

1. The Self-Correction Loop

How It Works

1. Claude acknowledges the mistake
2. Proposes a rule to prevent it
3. You approve → rule goes into memory
4. Future sessions avoid the same mistake

Add to CLAUDE.md

## Self-Correction Protocol

When the user corrects me or I make a mistake:
1. Acknowledge specifically what went wrong
2. Propose a concise rule: `[LEARN] Category: One-line rule`
3. Wait for approval before adding to LEARNED section

### LEARNED
<!-- Auto-populated through corrections -->

Trigger Phrases

• "Add that to your rules"
• "Remember this"
• "Don't do that again"

Example Flow

User: You edited the wrong file
Claude: I edited src/utils.ts when you meant src/lib/utils.ts.

[LEARN] Navigation: Confirm full path before editing files with common names.

Should I add this?

2. Parallel Sessions with Worktrees

Setup

# Create worktrees for parallel work
git worktree add ../project-feat feature-branch
git worktree add ../project-fix bugfix-branch

# Each gets its own Claude session
# Terminal 1: cd ~/project && claude
# Terminal 2: cd ~/project-feat && claude

When to Parallelize

Add to CLAUDE.md

## Parallel Work
When blocked on long operations, suggest starting a parallel session in a worktree.

3. The Wrap-Up Ritual

/wrap-up Checklist

1. Changes Audit - List modified files, uncommitted changes
2. State Check - Run

   git status

   , tests, lint
3. Learning Capture - What mistakes? What worked?
4. Next Session - What's next? Any blockers?
5. Summary - One paragraph of what was accomplished

Create Command

~/.claude/commands/wrap-up.md

Execute wrap-up checklist:
1. `git status` - uncommitted changes?
2. `npm test -- --changed` - tests passing?
3. What was learned this session?
4. Propose LEARNED additions
5. One-paragraph summary

4. Split Memory Architecture

Structure

.claude/
├── CLAUDE.md        # Entry point
├── AGENTS.md        # Workflow rules
├── SOUL.md          # Style preferences
└── LEARNED.md       # Auto-populated

AGENTS.md

# Workflow Rules

## Planning
Plan mode when: >3 files, architecture decisions, multiple approaches.

## Quality Gates
Before complete: lint, typecheck, test --related.

## Subagents
Use for: parallel exploration, background tasks.
Avoid for: tasks needing conversation context.

SOUL.md

# Style

- Concise over verbose
- Action over explanation
- Acknowledge mistakes directly
- No features beyond scope

5. The 80/20 Review Pattern

Review Points

1. After plan approval
2. After each milestone
3. Before destructive operations
4. At /wrap-up

Add to CLAUDE.md

## Review Checkpoints
Pause for review at: plan completion, >5 file edits, git operations, auth/security code.
Between: proceed with confidence.

6. Model Selection

Adaptive Thinking

Add to CLAUDE.md

## Model Hints
Escalate to Opus+Thinking when: first attempt failed, multi-system coordination, non-obvious bugs.
Use subagents with Haiku for fast read-only exploration, Sonnet for balanced work.

7. Context Discipline

Rules

1. Read before edit
2. Compact at task boundaries
3. Disable unused MCPs (<10 enabled, <80 tools)
4. Summarize explorations
5. Use subagents to isolate high-volume output (tests, logs, docs)

Context Compaction

• Auto-compacts at ~95% capacity (keeps long-running agents alive)
• Configure earlier compaction:

  CLAUDE_AUTOCOMPACT_PCT_OVERRIDE=50

• Use PreCompact hooks to save state before compaction
• Subagents auto-compact independently from the main session

Good Compact Points

• After planning, before execution
• After completing a feature
• When context >70%
• Before switching task domains

8. Learning Log

Add to CLAUDE.md

## Learning Log
After tasks, note learnings:
`[DATE] [TOPIC]: Key insight`

Append to .claude/learning-log.md

Learn Claude Code

What You'll Learn

Learning Path

1. Start — CLI shortcuts, context management, modes
2. Build — CLAUDE.md, writing rules, prompting, skills
3. Scale — Custom subagents, agent teams, hooks, MCP, GitHub Actions
4. Optimize — Pro-Workflow patterns 1-8, adaptive thinking, context compaction
5. Reference — Official docs for deep dives on any topic

Use /learn

/learn

Quick Setup

Minimal

## Pro Workflow

### Self-Correction
When corrected, propose rule → add to LEARNED after approval.

### Planning
Multi-file: plan first, wait for "proceed".

### Quality
After edits: lint, typecheck, test.

### LEARNED

Full Setup

git clone https://github.com/rohitg00/pro-workflow.git /tmp/pw
cp -r /tmp/pw/templates/split-claude-md/* ./.claude/
cp -r /tmp/pw/commands/* ~/.claude/commands/

Hooks

PreToolUse Hooks

PostToolUse Hooks

Session Hooks

Install Hooks

# Copy hooks to your settings
cp ~/skills/pro-workflow/hooks/hooks.json ~/.claude/settings.local.json

# Or merge with existing settings

Hook Philosophy

• Non-blocking - Hooks remind, don't block (except dangerous ops)
• Checkpoint-based - Quality gates at intervals, not every edit
• Learning-focused - Always prompt for pattern capture

Contexts

Agents

When to Delegate

• Task touches >5 files
• Architecture decision needed
• Requirements unclear

• Before committing
• PR reviews
• Security concerns

Custom Subagents

.claude/agents/

~/.claude/agents/

• Define with YAML frontmatter + markdown system prompt
• Control tools, model, permission mode, hooks, and persistent memory
• Use

  /agents

  to create, edit, and manage interactively
• Preload skills into subagents for domain knowledge

Agent Teams (Experimental)

• Enable:

  CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

• Lead session coordinates, teammates work independently
• Teammates message each other directly (not just report back)
• Shared task list with dependency management
• Display: in-process (Shift+Up/Down) or split panes (tmux/iTerm2)
• Delegate mode (Shift+Tab): lead coordinates only, no code edits
• Best for: parallel reviews, competing hypotheses, cross-layer changes
• Docs: https://code.claude.com/docs/agent-teams

MCP Config

• github

  - PRs, issues

• memory

  - Persist learnings

• filesystem

  - File ops

mcp-config.example.json

Commands

/wrap-up

/learn-rule

/parallel

/learn

/search

/list

/commit

/insights

Philosophy

1. Compound improvements - Small corrections → big gains
2. Trust but verify - Let AI work, review at checkpoints
3. Zero dead time - Parallel sessions
4. Memory is precious - Yours and Claude's