Skip to main content
Practical habits organized by frequency. Tested across Claude Code, Cursor, and Codex workflows.

​
Every Session

  • Run /doctor if things feel off
  • Check context with /context — know your budget
  • Name your session with /rename for easy /resume later
  • For returning tasks: /replay <topic> to surface past learnings
Don’t wait for auto-compact at 95% context usage — that’s the “dumb zone”. Manually compact at 50% for better performance.

​
Every Day

​
Update

1

Keep Claude Code Updated

It auto-updates, but check for new versions
2

Read the Changelog

Stay informed about new features
3

Review Your LEARNED.md

Prune stale rules that no longer apply

​
Terminal Setup

Use a Capable Terminal

  • iTerm2, Ghostty, Warp, or Kitty
  • Avoid IDE embedded terminals for heavy Claude Code sessions
  • tmux for split pane agent teams
  • Short alias: alias c='claude'

Monitor Usage

  • /usage to check plan limits
  • /cost for API key users
  • Watch for fast mode billing (charges extra usage from first token)

​
Every Week

​
Review Patterns

/insights  # See correction trends
Corrected often, but not yet learned. These should become rules.
Learned but never applied. Remove to reduce context noise.

​
Optimize CLAUDE.md

  • Keep root CLAUDE.md under 150 lines
  • Move specialized knowledge to package-level CLAUDE.md files
  • Move personal preferences to CLAUDE.local.md (gitignored)

​
Debugging Tips

  1. Try a different model — switch to Opus for hard problems
  2. Use ultrathink in your prompt for maximum reasoning
  3. Provide a screenshot (Claude is multimodal)
  4. Share browser console logs via MCP
  5. Start a fresh session with more targeted context

​
Environment Tips

​
Terminal Recommendations

TerminalPlatformWhy
iTerm2macOSSplit panes, tmux integration
GhosttymacOS/LinuxFast, GPU-rendered
WarpmacOSAI-native, blocks
KittyCross-platformGPU-rendered, scriptable
Windows TerminalWindowsWSL support

​
Voice Prompting

If you have voice mode access: 
/voice  # Enable voice mode
1

Hold Spacebar

Press and hold spacebar to start recording
2

Speak

Describe your request naturally
3

Release

Release spacebar to transcribe and send
Great for: describing bugs, architecture discussions, code reviews. Mix with typed input for precise file paths.

​
Tool Layering

The most productive setup uses multiple tools: 
Primary editor (Cursor/VS Code)
  ├── Tab completions for small edits
  ├── Inline chat for quick questions
  └── Claude Code in terminal for:
      ├── Multi-file changes
      ├── Debugging hard issues
      ├── Architecture decisions
      └── CI/CD and git operations

​
Anti-Patterns

Avoid these common mistakes:
Don’tDo Instead
Skip quality gates to save timeGates prevent more corrections later
Use dontAsk permission mode dailyUse default with specific allow rules
Load 15+ MCP serversKeep <10 active, disable unused
Compact mid-taskCompact at task boundaries
Fight the AI on styleAdd rules to CLAUDE.md instead
Use one huge CLAUDE.mdSplit into root + package-level files
Ignore the correction patternEvery correction is a learning opportunity

Build docs developers (and LLMs) love

Get started for freeTalk to us