Page 3 of 3
Mark deploy/ship/destructive skills so only an explicit /command runs them—Claude cannot auto-trigger them mid-session.
Cron a useful headless Claude task each morning: failing CI, stale PRs, and TODO hotspots—not an empty warmup.
Save repeatable workflows as SKILL.md (or .claude/commands) so you slash-invoke consistent PR reviews, releases, or checklists.
Declare a Compact Instructions section in CLAUDE.md so both manual /compact and autocompact preserve the project’s critical decisions by default.
Check in project settings so every teammate gets the same allow/deny rules, hooks, and env defaults without redoing /permissions.
Use /clear between unrelated tasks so leftover debugging does not bias the next feature.
Claude Code deletes session files older than 30 days at startup. If you have ever gone looking for a session you know you had, this setting is why it was gone.
Keep personal shortcuts and machine-specific notes in CLAUDE.local.md (gitignored) instead of polluting the shared CLAUDE.md.
Use /btw for single-turn clarifications that share full context but never enter conversation history or burn future tokens.
Claude Code adds a Co-Authored-By trailer to commits and an attribution line to pull requests. Set both to empty strings and it stops.
Run `/batch` on large mechanical migrations so Claude decomposes work and spawns per-unit worktree agents with PRs.
Add a top-level cache_control ephemeral flag so growing conversation prefixes reuse cached tokens and cut API cost and latency.
Auto-compact waits until your context is nearly full, which is well past the point where answer quality starts sliding. Set the window lower and compact while the session is still sharp.
"Never add comments" in CLAUDE.md plus "make this readable" in your prompt is a contradiction Claude has to resolve before it writes a line. Find those pairs and pick one.
Use /permissions to allowlist read-only and trusted commands so you stop mindlessly clicking Approve.
Most CLAUDE.md lines exist to correct a model that no longer makes that mistake. Delete them after an upgrade and re-add only the ones a failure proves you need.