One Claude Code Tip a Day: Explain the Codebase with Evidence
Use Claude Code to explain an unfamiliar codebase by demanding file-level evidence, runtime checks, and a second-pass correction instead of accepting a confident tour.
Read more每天一个 Claude Code 技巧
A daily English series sharing practical Claude Code tips, commands, and workflows.
One Claude Code Tip a Day: Switch Models Deliberately
Use /model as a workflow control, not a vanity setting: stay fast for exploration, switch up for plan review or tricky failures, then verify with tests and diffs before trusting the result.
Read more
One Claude Code Tip a Day: Compact Before Handoff
Use /compact as a deliberate handoff checkpoint: preserve the useful facts from a long Claude Code session, drop the noise, then verify the next step starts from the right assumptions.
Read more
One Claude Code Tip a Day: Clear Context on Purpose
Use /clear deliberately when a Claude Code session has accumulated stale assumptions, unrelated files, or failed debugging branches that would contaminate the next task.
Read more
One Claude Code Tip a Day: Ask /help Before You Guess
Use /help at the start of a Claude Code session to discover the commands, shortcuts, and workflow controls that are actually available instead of guessing from memory.
Read more
One Claude Code Tip a Day: Bootstrap the Repo Map
Do not treat /init as a checkbox. Use it to create a repo map, then verify commands, add failure notes, and make Claude Code read the project before editing.
Read more
One Claude Code Tip a Day: Critique the Plan First
A practical Claude Code field guide: make the model read the repo, critique its own plan, define verification, and only then edit code.
Read more