One Claude Code Tip a Day: Keep a Symptom-Cause-Fix Ledger
A practical Claude Code debugging habit: keep a small symptom-cause-fix ledger so logs, tests, UI checks, and second-pass corrections do not collapse into a single vague story.
Read more每天一个 Claude Code 技巧
A daily English series sharing practical Claude Code tips, commands, and workflows.
One Claude Code Tip a Day: Use @folder for Bounded Exploration
A field-guide habit for Claude Code: use @folder when a task lives in a feature area, then force Claude to map entry points, tests, and boundaries before editing.
Read more
One Claude Code Tip a Day: Make the Commit Message Prove the Diff
Do not let Claude Code write a decorative commit message. Make it read the diff, name the behavior, cite the proof, and expose skipped checks before you commit.
Read more
One Claude Code Tip a Day: Ask for a Verification Receipt
Do not accept “it works” from Claude Code. Ask for a verification receipt: commands, results, changed files, skipped checks, and the next correction when proof is missing.
Read more
One Claude Code Tip a Day: Make Claude Predict the Diff
Before Claude Code edits, ask it to predict the diff: files, shape, tests, and no-touch areas. Then compare the real git diff to that forecast before accepting the patch.
Read more
One Claude Code Tip a Day: Draw the Dependency Boundary
Before Claude Code edits a shared module, make it map the callers, imports, tests, and no-touch edges. The boundary turns a risky refactor into a reviewable session.
Read more
One Claude Code Tip a Day: Check /cost Before the Session Sprawls
Use /cost as an engineering checkpoint in Claude Code: notice when a session is sprawling, then narrow the next proof, switch strategy, or stop before more tokens become more confusion.
Read more
One Claude Code Tip a Day: Keep a Decision Log in the Thread
Use Claude Code to keep a decision log during real work: record assumptions, rejected options, evidence, and corrections so the final diff is easier to review and safer to ship.
Read more
One Claude Code Tip a Day: Redact Secrets Before Debugging
Debug auth and deployment failures with Claude Code without pasting secrets: map variable names, redact logs, inspect config paths, and make the final diff prove no credentials leaked.
Read more
One Claude Code Tip a Day: Make Migrations Boring
Use Claude Code as a migration safety partner: inspect the current schema first, demand a boring migration plan, run dry checks, verify app code, and write the rollback note before deployment.
Read more