My 10 Pro Tips for Claude Code users
By StormDragon762 · DISCUSSION · About Claude Code
My "cheat sheet" for Claude code, sharing here with y'all and hoping to get your cheat sheets in return! Ty!
**1/10**
Use /effort high then include “ultrathink” in your prompt. This forces full extended thinking with a 31,999-token budget.
**2/10**
End every important session with a clear “Summary of learnings” paragraph. The background Dream system (Auto-Memory) will automatically extract it and inject it into future sessions.
**3/10**
/fork <name> creates a fully isolated conversation branch with its own plan files and transcripts. /rewind undoes the last turn — including any code changes.
**4/10**
Tell Claude to “start an Explore agent” or “enter Plan mode.” The state manager instantly injects the correct role instructions and tool restrictions.
**5/10**
Always use absolute paths. Sub-agents and worktrees enforce this strictly — relative paths cause friction and errors.
**6/10**
Set up custom hooks in .claude/settings.json. Use exit code 2 in a PostToolUse or PreToolUse hook to silently block actions and force a rewind.
**7/10**
/fast does not change the model — it runs the same Opus with faster output. Pair it with /effort medium for the best speed/quality balance.
**8/10**
Keep \~/.claude/debug/latest open with tail -f. It shows every trigger, whisper injection, and state-manager decision in real time.
**9/10**
Run your own local MCP servers. They let you expose custom tools and use elicitation to pause the agent mid-task for structured user input.
**10/10**
Prefix important instructions with <system-reminder> tags. Because of the prompt assembly order, the model treats them with the same priority as internal whispers.
261 upvotes · 6 comments
Comments (6)
NeonVibe275: Use Superpowers
SwiftEcho377: claude --dangerously-skip-permissions
SolarSurfer919: solid list. one thing id add is using CLAUDE.md files per module for the really dangerous directories like auth and billing. claude reads those automatically when it works in that folder so it knows the constraints without you having to repeat them every session
SwiftMaker840: Great list. One thing that leveled up my workflow was adding a Workflow Orchestration section to CLAUDE.md — basically rules like "enter plan mode for any non-trivial task" and "never mark a task complete without proving it works." Claude Code reads those instructions every session, so it enforces d
DigitalHawk9933: write a [SKILL.md](http://SKILL.md) file for repeated workflows. I have one for property / investments. Claude just follows the steps each time and i dont have to keep repeating myself!!
ShadowEcho853: I've never had an issue using relative paths
More discussions about Claude Code on HonestUse