Claude Code

# 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"
  }
}

Keyboard shortcuts

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

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.

System prompt evolution

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