20 Claude Code Tips

1 · Run /init

It creates a CLAUDE.md file describing your project, commands, and conventions. Claude reads it at the start of every session.

2 · Keep CLAUDE.md short

Add build and test commands, style rules, and things Claude keeps getting wrong. Remove anything outdated.

3 · Point to files with @

Mention files with @ so Claude reads exactly what matters instead of searching.

4 · Paste screenshots

Paste an image of a design or an error. It is often faster than describing it.

5 · Use plan mode

Press Shift+Tab to cycle modes and pick plan mode. Claude researches and proposes a plan without editing files.

6 · Ask for tests first

For bigger changes, ask Claude to write or update tests, then make them pass.

7 · Give a clear finish line

Say what done looks like: “The page loads, tests pass, and nothing else changes.”

8 · Use /clear between tasks

A fresh context for each new task keeps answers focused and saves tokens.

9 · Use /compact on long sessions

It summarizes the conversation so you can keep going with less context.

10 · Pick the right model and effort

Use /model to switch. Use bigger models and higher effort for hard problems, and smaller ones, such as Haiku 5.5, for quick tasks.

11 · Press Esc to stop

Interrupt Claude as soon as it heads the wrong way, then redirect it.

12 · Rewind with checkpoints

Press Esc twice, or use /rewind, to go back to an earlier point in the conversation and code.

13 · Resume past sessions

Use /resume, or start with claude --continue, to pick up where you left off.

14 · Use subagents

Subagents handle side tasks, such as searching or reviewing, in their own context. Since October 2026, you can set the effort level a subagent runs at.

15 · Turn repeat work into skills

Save instructions for tasks you repeat as skills or slash commands, so you never retype them.

16 · Add hooks

Hooks run your own commands at set moments, such as formatting code after every edit.

17 · Connect MCP servers and plugins

Connect tools such as GitHub, databases, or docs with MCP. Install plugins from marketplaces, and use mods, added in October 2026, to change how Claude Code itself behaves.

18 · Set permissions once

Allow safe, frequent commands, such as running tests, so Claude stops asking. Keep risky commands on ask.

19 · Run in parallel with worktrees

Use separate git worktrees so several sessions can work on different tasks without clashing.

20 · Go headless

Run claude -p "your prompt" in scripts and automations for one-off tasks without the interactive screen.