Speed Up Claude Code: Fix the 3 Habits Slowing You Down
TL;DR
A slow session is almost never the model. It is three habits: letting Claude code blind instead of planning first, retyping the same context every session instead of saving it once, and rewriting prompts you already got right. Fix all three and the same work takes a fraction of the time. This is the exact three-step fix, with copy-paste files.
It is the habits, not the model
When Claude feels slow, the instinct is to blame the model or reach for a bigger one. That is almost always wrong. The real cost is three small habits that turn a clean one-shot build into a messy back-and-forth. Fix the habits and you stop paying the tax on every single session.
Trap 1: Skipping plan mode
Letting Claude start coding before it has a plan means it charges off in a direction you did not want, and you spend the next twenty minutes steering it back. One plan-mode pass first turns a messy redo into a clean build. Ask for the plan, read it, correct it once, then let it run.
Trap 2: Re-explaining everything every session
Typing the same context - your stack, your conventions, where things live - at the start of every session burns your time and your tokens. Say it once in a CLAUDE.md file at the root of your project and Claude reads it automatically in every chat after. You stop being the model's memory.
markdown# CLAUDE.md
## Stack
[e.g. Next.js 15, TypeScript, Tailwind, Supabase]
## Conventions
- [e.g. Use the Edit tool, never rewrite whole files]
- [e.g. No new dependencies without asking]
## Where things live
- [e.g. Components in src/components, API routes in src/app/api]
## What to never do
- [e.g. Never commit .env, never push without asking]Trap 3: Throwing away good prompts
Rewriting a prompt you already nailed is pure waste. Save it as a slash command and reuse the win with one word instead of a paragraph. Drop a markdown file in .claude/commands/ and it becomes a command you can fire any time.
markdown# .claude/commands/review.md
Review the code I just changed. Check for: bugs, security
issues, and anything that does not match CLAUDE.md. List
problems by severity. Do not fix anything until I say so.Common questions
Does a bigger model make Claude faster?
Usually not for the problem you actually have. A slow session is normally caused by unclear direction and repeated context, not raw model speed. Fix the three habits first - most people find the model was never the bottleneck.
What is plan mode?
It is asking Claude to lay out its approach and the files it will touch before it writes any code, so you can correct the direction in seconds instead of unwinding a finished-but-wrong build. You can trigger it with a plain instruction like the one in Trap 1.
Where does a CLAUDE.md file go?
In the root of your project. Claude Code reads it automatically at the start of every session. See our Ultimate CLAUDE.md File guide for a full template.
How do slash commands work?
Each markdown file in .claude/commands/ becomes a command named after the file. Put your best reusable prompt inside, then invoke it by name instead of retyping the paragraph.
Want the rest of the setup that makes Claude fast by default?
Get the other 17 in the starter stack, plus 5,000+ builders - $9/mo, cancel anytime.
Join the Club