Claude Code ships updates almost weekly. If you installed it even a month ago, there's a good chance several features dropped after your setup. Two minutes of catching up will change how you use it.
WHAT THIS IS:
A walkthrough of built-in Claude Code features that don't show up in any onboarding flow. They're live right now. You just have to know they exist.
WHY IT MATTERS:
Each of these saves real time on real work. CLAUDE.md alone changed how I start every project. Hooks automate things I used to do manually every single time. These aren't nice-to-haves. They're the gap between using Claude Code and actually getting results from it.
HOW TO USE IT:
1. CLAUDE.md
Create a file called CLAUDE.md in your project root. Put your preferences, coding standards, and project context in it. Claude reads this automatically at the start of every conversation. You teach it once, it remembers every session. Or run /init and let Claude generate one for you by analyzing your codebase.
2. /cost
Type /cost to see exactly what you've spent in the current session. Tokens in, tokens out, running total. No surprises.
3. Plan Mode
Press Shift+Tab before a big task. Claude will think through the approach and show you a structured plan before writing any code. Review it, adjust it, then let it execute. This prevents the "it built the wrong thing for 20 minutes" problem. You can also type /plan to enter it directly.
4. Hooks
Shell commands that fire automatically when Claude does something. Want to auto-format every file after an edit? Run tests after every code change? Block dangerous commands before they execute? Hooks handle all of it. Configure them in .claude/settings.json. They're deterministic. They fire every time, regardless of what the model decides to do.
5. Memory
Claude Code persists notes across sessions in ~/.claude/ and loads them automatically. When you correct it or state a preference, it saves that and applies it in every future conversation. I told mine once to never use em dashes in my writing. It hasn't used one since. Type /memory to view or edit what it has stored.
6. MCP Servers
Model Context Protocol lets you connect Claude Code to external services. GitHub, databases, browsers, APIs. I have mine connected to GitHub and a browser automation tool. Claude can open pull requests and check live pages without me switching windows. Add servers in your settings or run /mcp to manage connections.
TRY THIS:
Open your terminal. Run claude in any project directory. Type /init and let it generate a CLAUDE.md for your project. Then type /help to see every slash command available. Two minutes, and you'll immediately spot features you didn't know were there.