Claude Code Tips and Tricks: 12 Ways to Use Claude Code Effectively

Claude Code has quietly become the tool a lot of us live in all day — and not just programmers. People use it to maintain websites, clean up spreadsheets, automate boring chores, and build things they never thought they could build. But most tips lists out there are written for software engineers, full of jargon about hooks and configs.

This one isn't. These are twelve practical Claude Code tips and tricks — useful whether you're a beginner or you already spend hours a day in the terminal — for using Claude Code effectively without an engineering degree.

1. Always start in the right folder

Claude Code works inside whatever folder you open it from. Starting it from your home folder gives it a confusing view of your entire computer. Before you type claude, move into the project folder you actually want to work on (type cd, a space, then drag the folder onto the terminal and press Enter). Everything — context, memory, even notifications — works better from a project folder.

2. Brief it like a colleague, not a search engine

"Fix the About page" forces Claude to guess what's wrong. "The About page shows the team photos in the wrong order — founders should come first, and the layout breaks on phones" gets it right the first time. The one extra sentence of context you give upfront routinely saves a ten-minute round trip.

3. Use Plan Mode for anything big

Press Shift+Tab twice and Claude Code switches into Plan Mode: it reads everything, thinks, and presents a plan — without changing a single file. You review the plan in plain English, adjust it, and only then let it work. For anything that touches more than a couple of files, this is the difference between delegating and gambling.

4. Keep a briefing file (CLAUDE.md)

There's a special file called CLAUDE.md that Claude reads at the start of every session — think of it as a standing briefing document. What the project is, how you like things done, what to never touch. You don't have to write it yourself: type /init once and Claude drafts it for you. Every session after that starts smarter.

5. Clear the slate between unrelated tasks

When you finish one task and start something unrelated, type /clear. Long, winding conversations make Claude slower and more forgetful — a fresh start with a clear head beats dragging two hours of old context into a new problem.

6. Interrupt early instead of waiting politely

If you can see Claude going down the wrong path, press Escape. It stops immediately and waits for new directions. Letting a wrong approach finish just so you can correct it afterwards wastes the whole run — steering early is always cheaper.

7. Stop watching it work

This is the tip that changes the day-to-day the most. A serious Claude Code task runs for several minutes, and the terminal is silent the whole time. So you either sit there watching text scroll — or you switch to something else and miss the moment it finishes (or worse, the moment it pauses to ask your permission and sits blocked while you're answering email).

Heavy users solve this with notifications. We built AI Done Now for exactly this: a Mac menu bar app that plays a sound and shows a clickable notification when Claude Code finishes or needs your input — with different alerts for "done" and "waiting for you", so you know whether to come back now or finish your coffee.

8. Treat permission prompts as your safety net

Claude Code asks before doing anything consequential — running commands, deleting things, installing software. Don't rush to approve everything blindly, and don't switch on "skip all permissions" modes you may see mentioned online. Those prompts are the moments you stay in control without needing to understand the code itself.

9. Run a second session

Nothing says you can only have one Claude Code running. Open a second terminal tab in a different project folder and you've doubled your output — one session redesigns your site while another cleans up your files. It takes a little organization (we wrote a full guide to running multiple Claude Code sessions), but it's how extensive users get so much done.

10. Ask it to explain anything, anytime

You never need to pretend you understood. "Explain what you just changed like I'm not a programmer" is a completely valid prompt, and Claude is genuinely good at it. Make it a habit after every big change — you'll learn your own project faster than you expect.

11. Ask for save points before big changes

Before Claude attempts something risky, say: "make a checkpoint first so we can undo this if it goes wrong." Claude uses a system called git to snapshot your project, and it handles the details for you. If the experiment fails, one sentence — "go back to the checkpoint" — restores everything.

12. Use it for the un-glamorous stuff too

Claude Code isn't only for building things. Renaming five hundred photos, merging spreadsheets, converting file formats, drafting a README — the boring chores you've postponed for months are usually one prompt away. Some of the happiest Claude Code users barely "code" with it at all.

The common thread

Every tip here points the same direction: treat Claude Code less like a chatbot you babysit and more like a capable colleague you brief, check in on, and trust to work while you do something else. Set up the briefing file, plan before big jobs, run a parallel session — and let notifications tell you when you're needed, instead of your eyes.