One Claude Code Tip a Day: Keep Team Rules in /memory
Use /memory for durable team rules—verification commands, style constraints, deployment cautions—not for every theory from today’s debugging session.
Read moreClaude Code
A collection of 54 posts
One Claude Code Tip a Day: Use /compact Before the Signal Gets Buried
Use /compact as a deliberate checkpoint in long Claude Code sessions: keep the bug, evidence, decisions, diff, and verification path while dropping the noise.
Read more
One Claude Code Tip a Day: Turn Failed Checks Into the Next Prompt
When a check fails, do not ask Claude Code to “fix it.” Paste the exact failure, freeze the scope, request one hypothesis, and make the next patch prove that signal changed.
Read more
One Claude Code Tip a Day: Turn Repeated Prompts Into Slash Commands
When you paste the same review or verification prompt for the third time, promote it into a project slash command with allowed tools, arguments, and a checklist tied to real evidence.
Read more
One Claude Code Tip a Day: Write the File Contract Before Editing
Before Claude Code edits a busy file, make it state the file contract: responsibilities, callers, invariants, side effects, and proof commands. Then review the patch against that contract.
Read more
One Claude Code Tip a Day: Use /clear Before the Context Turns Muddy
Use /clear when a Claude Code session has accumulated wrong assumptions, failed fixes, and stale logs. Restart with a clean brief, not a clean memory.
Read more
One Claude Code Tip a Day: Keep a Repro Transcript
Before asking Claude Code to fix a bug, capture the exact repro path, command output, expected behavior, and one failed attempt. A repro transcript turns a vague debugging session into a focused loop.
Read more
One Claude Code Tip a Day: Keep a Rollback Note Beside the Diff
Make Claude Code keep a rollback note next to the git diff: what changed, how to undo it, what proof is missing, and when to revert instead of piling on fixes.
Read more
One Claude Code Tip a Day: Set a Stop Condition Before Another Patch
Before Claude Code makes another patch, define the signal that forces it to stop: a repeated failing test, an unexplained log line, a widened diff, or evidence that the first theory was wrong.
Read more
One Claude Code Tip a Day: Gate Risky Commands With /permissions
Use Claude Code permissions as a deliberate safety gate: approve boring inspection, pause before destructive commands, and turn risky operations into reviewed checkpoints.
Read more