Claude Code Tips That Actually Make a Difference

This isn’t a rehash of the docs. If you want installation steps and “what is Claude Code,” I already wrote that — go read the beginner tutorial first.

This is for people who have been using Claude Code for a bit and want to stop doing things the slow way. These are the shortcuts, modes, and prompts I actually use in real projects.

Here are the ones I would set up first if I were starting over today.

Tip 1: Skip the Chat — Pass Your Task Directly

Most people open Claude Code and then type their request. That’s an extra step you don’t need.

You can pass your task straight from the command line when you launch it:

claude "add a contact form to the homepage"

If you’ve set up the c shortcut from my skip-permissions guide, it’s even shorter:

c "add a contact form to the homepage"

Claude opens, reads your project, and starts working immediately. No chat window, no waiting for a prompt. You tell it what to do and it goes.

Tip 2: Pick Up Where You Left Off

I close terminal sessions all the time — tmux windows get cleaned up, SSH sessions drop, laptops get closed. Being able to pick up exactly where I left off saves me constantly.

There are two ways to do this:

claude --resume opens the resume picker. You can also resume a specific session by name or ID if you know it:

claude --resume

claude --continue (or just claude -c) skips the picker and jumps straight back into your most recent session:

claude --continue

Use --resume when you need to find a specific conversation from earlier. Use --continue when you just accidentally closed the terminal and want to get back to what you were doing.

Tip 3: Make Claude Think Before It Writes

This is one of my most-used features. Press Shift+Tab inside a Claude Code session to toggle plan mode.

In plan mode, Claude can inspect the codebase, analyze the problem, and present an implementation plan before it touches a file. That separation matters. The best workflow is still boring: explore first, plan second, implement third, verify last.

If you want to revise the plan before implementation, use Ctrl+G to open it in your editor, clean it up, and then send Claude back to work from a better starting point.

When to use it:

• Starting a new feature that touches multiple files
• Working on unfamiliar code you didn’t write
• Complex refactors where you want to see the approach first
• Anything where getting it wrong means a painful rollback

When to skip it:

• Quick bug fixes where you already know the problem
• Simple tasks like renaming a variable or updating a string
• Anything you could describe in one sentence

I use plan mode for anything that touches more than two files. It is the difference between Claude charging ahead with a plausible-but-wrong change and Claude actually understanding the codebase first.