20 Claude Code Tips

1 · Run /init

It generates a CLAUDE.md file that describes your project, commands, and conventions. Claude reads it at the start of each session.

2 · Keep CLAUDE.md lean

List build and test commands, style rules, and the things Claude keeps getting wrong. Cut anything outdated.

3 · Reference files with @

Mention files with @ so Claude reads exactly what matters instead of hunting for it.

4 · Paste screenshots

Paste an image of a design or an error. That is often quicker than describing it.

5 · Use plan mode

Press Shift+Tab to cycle through modes and choose plan mode. Claude researches and proposes a plan without touching files.

6 · Start with tests

For larger changes, have Claude write or update tests first, then make them pass.

7 · Define a clear finish line

Spell out what done means: “The page loads, tests pass, and nothing else changes.”

8 · Run /clear between tasks

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

9 · Run /compact in long sessions

It condenses the conversation so you can continue with less context.

10 · Match the model and effort to the task

Switch with /model. 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 the moment it heads the wrong way, then point it back on course.

12 · Rewind to a checkpoint

Press Esc twice, or run /rewind, to return to an earlier point in both the conversation and the code.

13 · Pick up past sessions

Run /resume, or start with claude --continue, to continue where you stopped.

14 · Delegate to subagents

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

15 · Turn repeated work into skills

Save instructions for recurring tasks as skills or slash commands, so you never type them twice.

16 · Add hooks

Hooks run your own commands at set points, such as formatting code after each edit.

17 · Connect MCP servers and plugins

Connect tools such as GitHub, databases, or docs through 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 about them. Keep risky commands on ask.

19 · Work in parallel with worktrees

Use separate git worktrees so several sessions can tackle different tasks without colliding.

20 · Run headless

Run claude -p "your prompt" in scripts and automations for one-off tasks, with no interactive screen.