📌 TL;DR
If you’re using Claude Code without these 5 features, you’re using it at half capacity.
Most of them ship in the box, but a surprising number of devs don’t know they exist.
I picked the ones that got the most traction in the community.
Are you using Claude Code as just a “terminal tool that talks to an AI”? If so, this post is for you. I’ve collected the productivity tips that got real traction on Reddit’s r/ClaudeAI and on GitHub.
💡 1. /init to auto-generate CLAUDE.md
When you open Claude Code in a fresh repo, a single /init command analyzes the whole project and generates a CLAUDE.md file.
Why does this matter? CLAUDE.md is auto-injected into context at the start of every session. You stop having to repeat “this project is React + TypeScript, the API lives here, …” every single time.
💡 2 minutes on /init saves 10–15 minutes per session afterward. Claude already knows your project structure, stack, and conventions before you type a thing.
You can also drop team conventions or “don’t touch this file” rules into CLAUDE.md. Claude reads it at the start of every session.
💡 2. Plan Mode — design before you write code
Shift+Tab toggles between Plan Mode and normal mode.
In Plan Mode, Claude doesn’t touch your code. Instead, it analyzes the codebase, maps dependencies, and lays out an execution plan. You review and edit the plan, then run it.
⚠️ 2 min plan + execute vs execute now + 20 min refactor — the first one almost always wins, especially when the change spans multiple files.
Make Plan Mode a habit before any complex feature or refactor. You’ll dramatically cut down on “Claude went the wrong direction and rewrote half the file” moments.
💡 3. /btw — side questions without breaking the flow
Added in March 2026. While Claude is in the middle of a long task, type /btw to ask a side question without interrupting the work in progress.
For example, while Claude is writing test code:
/btw any reason this project uses vitest instead of jest?
Ask that, and the original work keeps going while Claude answers separately. It’s short for “by the way,” and in practice it keeps your flow from breaking.
💡 4. /clear — kill session contamination
Run several different tasks back-to-back in the same session and the context starts blending. The previous task’s framing leaks into the next one and you get weird outputs.
/clear resets the session cleanly. CLAUDE.md stays loaded; only the conversation context is wiped.
❌ Avoid the “kitchen sink session.” Bug fix → new feature → docs all in one session is a fast track to Claude confusing the previous task’s context with the current one.
Hit /clear every time the task type changes. This single habit kills most of the “why did Claude suddenly write something bizarre?” moments.
💡 5. MCP for external tool integration
MCP (Model Context Protocol) lets you wire external tools into Claude Code. The most popular one is Context7, which pulls the latest official docs for any tech, on demand.
Say “migrate this to Next.js 15’s new routing,” and Context7 fetches the Next.js 15 official docs in real time so Claude writes against the current API instead of stale training data.
💡 As one Reddit comment put it: not using MCP is like “driving a Ferrari in first gear.”
Setup is a few lines in the Claude Code config — add the MCP server entry. There are curated lists of popular MCP servers on GitHub worth scanning.
💬 My take
The two with the biggest impact, by far, are CLAUDE.md and Plan Mode. Both run on the same idea — invest in prep, execution gets faster — and that principle carries straight over into AI-assisted coding.
/clear was the one I picked up last, and honestly, knowing only that one would have eliminated half my “Claude is producing garbage” sessions. New task type? /clear. That’s it. That’s the rule.
❓ FAQ
Q. Is Claude Code free?
It’s available on Claude Pro ($20/month) and up. The Max plan ($100/month) gets you much more generous usage limits. You can also bring your own API key, in which case you pay per usage.
Q. What should I put in CLAUDE.md?
Start with /init for the baseline, then layer in team conventions (code style, naming, banned patterns), project quirks, and rules like “don’t touch this directory.” Claude reads it automatically every session.
Q. Is MCP setup hard?
It’s adding a few lines of JSON to a config file. The official Claude Code docs have a step-by-step guide, and popular MCP servers like Context7 ship clear setup examples in their READMEs.
🔗 Related links
→ Claude Code Official Best Practices
→ GitHub — 45 Claude Code Tips
This post was written based on information available as of April 15, 2026. I aim for accuracy, but given how fast this space moves, some details may have been updated since. Check the source links above for the latest.
This post is part of an English mirror of a Korean dev experiments blog. Cross-posted for the global developer audience.