A collection of 54 posts
Use Claude Code to add small guardrail tests around the seam you are about to change: read behavior first, write characterization tests, verify failure signals, then edit with confidence.
Read more
Use Claude Code to update README docs from verified project reality: inspect commands, run checks, patch only proven instructions, and review the documentation diff like code.
Read more
A field guide to starting Claude Code in the correct repository: prove where you are, inspect git state, map the active app, and prevent confident edits in the wrong checkout.
Read more
Use /cost as a debugging checkpoint: when a Claude Code session turns into a loop, measure the spend, narrow the next prompt, inspect the diff, and buy certainty instead of motion.
Read more
Use Claude Code to ship small features safely: define the visible behavior, inspect the existing path, patch the narrowest seam, and verify with tests, logs, and git diff before expanding scope.
Read more
Use Claude Code to debug from the first real error instead of the loudest symptom: reproduce, inspect the stack trace, make a narrow fix, and verify with a second pass.
Read more
Use Claude Code for refactoring by slicing one behavior-preserving change at a time, verifying each step with tests, logs, and git diff before asking for the next move.
Read more
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
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
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