Claude Code has a hidden power level most devs never unlock.
I read the full docs. Here's the cheat sheet:
𝟭. "𝘂𝗹𝘁𝗿𝗮𝘁𝗵𝗶𝗻𝗸"
❌ "design a backend"
✅ "ultrathink: design a scalable backend for 10k users with DB, caching, scaling"
One word prefix. 10x better output.
𝟮. /𝗯𝘁𝘄
Side question without killing your context.
/btw how does token refresh work in OAuth2
Answers instantly. Main task untouched.
𝟯. 𝗣𝗹𝗮𝗻 𝗠𝗼𝗱𝗲
claude --permission-mode plan
Claude plans first. You edit. THEN it codes.
No more surprise refactors.
𝟰. 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗠𝗼𝗱𝗲
"Interview me using AskUserQuestion. Ask about edge cases and tradeoffs."
It asks questions you forgot to think about.
Then writes a better spec than most PMs.
𝟱. 𝗦𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀
❌ "check my codebase" (47 files dumped)
✅ "Use subagents to investigate auth handling"
Clean summary. Context preserved.
𝟲. /𝗰𝗼𝗺𝗽𝗮𝗰𝘁 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗫
Context bloated?
/compact Focus on API changes and failing tests
Keeps signal. Drops noise.
𝟳. 𝗘𝗳𝗳𝗼𝗿𝘁 𝗹𝗲𝘃𝗲𝗹
export CLAUDE_CODE_EFFORT_LEVEL=high
One env variable. Permanently deeper thinking.
𝟴. 𝗪𝗿𝗶𝘁𝗲𝗿/𝗥𝗲𝘃𝗶𝗲𝘄𝗲𝗿
Session 1: "Implement rate limiting"
Session 2: "Review for race conditions"
Two sessions > one trust-and-pray session.
𝟵. --𝗳𝗿𝗼𝗺-𝗽𝗿
claude --from-pr 247
Restores full PR context. Zero re-explaining.
𝟭𝟬. .𝘄𝗼𝗿𝗸𝘁𝗿𝗲𝗲𝗶𝗻𝗰𝗹𝘂𝗱𝗲
Add .env files once. Auto-copied to every worktree.
Never debug a missing key at 2am again.
—
Most devs use AI like autocomplete.
The ones shipping fast use it like a 𝗷𝘂𝗻𝗶𝗼𝗿 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝘁𝗵𝗲𝘆 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗺𝗮𝗻𝗮𝗴𝗲.
Bookmark this. You'll need it.
I write about distributed systems, blockchain infra, and dev tooling that actually makes you faster.
If your team is solving interesting protocol/infra problems → let's chat.
🔗 @0x_Samrat
English
