Workflow

The daily workflow for using Claude Code Setup effectively.

Overview

┌─────────────────────────────────────────────────────────┐
│  SESSION START                                          │
│                                                         │
│  /catchup → See what changed, what's next               │
└─────────────────────────────────────────────────────────┘
                          │
                          ▼
┌─────────────────────────────────────────────────────────┐
│  WORK                                                   │
│                                                         │
│  Implement tasks from CLAUDE.md                         │
│  /todo → Quick capture, /design for complex features    │
│  Monitor context: Ctx: 70% (via ccstatusline)           │
└─────────────────────────────────────────────────────────┘
                          │
                          ▼
┌─────────────────────────────────────────────────────────┐
│  SESSION END (when context fills up)                    │
│                                                         │
│  /wrapup → Saves status to CLAUDE.md, commits           │
│  /clear → Fresh start with full memory                  │
└─────────────────────────────────────────────────────────┘

Session Start

After /clear or New Chat

/catchup

Claude will:

Read your project’s CLAUDE.md
Check recent Git changes
Load relevant Records
Load coding standards for your tech stack
Show you what’s next

First Time on a Project

/init-project

Creates the project CLAUDE.md and docs/records/ folder.

During Work

Track Important Decisions

When Claude makes a significant decision, add it to Records:

Create a Record for why we chose JWT over sessions

For small decisions with a quick “why”:

Add to Recent Decisions: pip --user to avoid PEP 668 error

Add New Tasks

/todo Add password reset functionality

Claude determines if it needs a Record or just a table entry.

Corrections Are Saved Automatically

When you correct Claude or share project knowledge, it gets saved so it survives /clear:

Correction type	Saved to
Personal preferences (“I prefer German commits”)	User Instructions (global)
Project preferences (“always use pytest-asyncio”)	Project Instructions
Project facts (“API expects ISO-8601”)	Recent Decisions
Session context (“Bug is in Auth module”)	Private Note

Signs to Re-Plan

Claude notices when the current approach isn’t working:

Third workaround for the same problem
Something invalidates an earlier assumption
Scope growing well beyond the original task

When this happens, Claude pauses and reconsiders instead of pushing through with workarounds.

Monitor Context

Watch the status line:

Ctx: 45% | Model: opus | Branch: main

At ~80%, it’s time to wrap up.

Session End

Save Your Progress

/wrapup