🪴 Zero's Garden

Claude Code

3 min read

CCometixLine

# https://docs.claude.com/en/docs/claude-code/setup
curl -fsSL https://claude.ai/install.sh | bash
 
# fancy statusline
git clone https://github.com/Haleclipse/CCometixLine.git
cd CCometixLine
cargo build --release
 
mkdir -p ~/.claude/ccline
cp target/release/ccometixline ~/.claude/ccline/ccline
chmod +x ~/.claude/ccline/ccline
 
 
# then edit your `.claude/settings.json` https://docs.claude.com/en/docs/claude-code/statusline
{
  "statusLine": {
    "type": "command",
    "command": "~/.claude/ccline/ccline",
    "padding": 0
  },
  "env": {
    "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": "1"
  }
}

Short-lived node process

CCometixLine calls npm view, which fetches the latest Claude Code version from the npm registry - this happens when the usage segment is enabled.

Config

  1. It’s recommended to disable auto-compact and “micromanage” the context window of each session, unless you need very long sessions of YOLO mode.

Keyboard shortcuts

  • Ctrl+R to search prompt history, and Esc to modify the selected prompt.

Plan usage limits

https://support.claude.com/en/articles/11145838-using-claude-code-with-your-pro-or-max-plan

Reference prompts

(In plan mode)
> I need to refactor our authentication system to use OAuth2. Create a detailed migration plan.

...

> Create a detailed MIGRATION_PLAN.md file that includes:
- All migration phases and steps
- Dependencies between steps
- Estimated effort for each phase
- Success criteria and checkpoints
- Any risks or considerations

This will help me track progress across multiple sessions.

Compare your xxx changes with other files in the same directory. Does your implementation match existing conventions?

Review Phase 5 Checkpoint in MIGRATION_PLAN.md to see if it has been correctly implemented.

Update MIGRATION_PLAN.md accordingly. Only fix discrepencies and keep the implementation status unchanged.
Don't include "changed xxx" phrases. Instead, focus on guiding someone who wants to implement this from scratch without our reference implementation.
Don't include complete file content as it would limit divergent thinking.

https://boristane.com/blog/how-i-use-claude-code/:

read this folder in depth, understand how it works deeply, what it does and all its specificities. when that’s done, write a detailed report of your learnings and findings in research.md

study the notification system in great details, understand the intricacies of it and write a detailed research.md document with everything there is to know about how notifications work

go through the task scheduling flow, understand it deeply and look for potential bugs. there definitely are bugs in the system as it sometimes runs tasks that should have been cancelled. keep researching the flow until you find all the bugs, don’t stop until all the bugs are found. when you’re done, write a detailed report of your findings in research.md

Notice the language: “deeply”, “in great details”, “intricacies”, “go through everything”. This isn’t fluff. Without these words, Claude will skim. It’ll read a file, see what a function does at the signature level, and move on. You need to signal that surface-level reading is not acceptable.

Let Claude Code name the file:

Write it to docs/*.md

System prompt evolution

https://github.com/marckrenn/cc-mvp-prompts

Graph View

Backlinks