Claude Code Efficiency

Claude Code Efficiency Playbook: Ship 10x Faster

Claude Code Efficiency

25 battle-tested tips from 800+ hours of Claude Code usage. Compiled from 4 expert sources + official docs. Organized by skill level.

What it does Claude reads your entire codebase and generates a starter CLAUDE.md with project conventions, tech stack, and key patterns.

Why it matters Without /init, Claude guesses your project structure on every message. With it, Claude already knows your stack, test runner, linter config, and file layout before you ask anything.

Sources: John Kim, Edmund Yong

What it does Press # during any session to append rules, preferences, or conventions directly to CLAUDE.md without leaving the terminal.

Why it matters When Claude does something you don't like, correct it once and make it permanent. No context switch, no file editing. The rule applies to every future session.

Sources: Official Docs

What it does Before executing anything, Claude gathers information, reads files, and presents a structured plan for your approval.

Why it matters Without plan mode, Claude dives straight into code changes. With it, you catch wrong assumptions before a single file is touched. The key: edit the plan, don't just approve it.

"I use plan mode almost exclusively for new features. Let Claude think before it writes."

Sources: Edmund Yong, Jaymin West

What it does Constrains your project instructions to only the most critical rules, using .claude/rules/ for everything else.

Why it matters More rules does not mean more compliance. A 50-line file followed 100% of the time beats a 500-line file followed 40%. Claude has finite attention. Front-load what matters most.

Sources: John Kim, Official Docs

What it does Claude automatically runs your build and test commands after every change, self-corrects on failure, and retries until everything passes.

Why it matters This is the single most important pattern for automated AI loops. Without it, Claude writes code that looks right but doesn't compile. With it, Claude catches its own mistakes and fixes them before presenting results.

"The validation loop is the single most important thing for automated AI loops."

Sources: Edmund Yong, John Kim, Official Docs

What it does Compresses your entire conversation context into a summary while keeping CLAUDE.md and system rules active.

Why it matters Don't start a new chat when context fills up; you lose accumulated understanding. /compact preserves the important context while freeing space for more work. Claude remembers what it built, just compressed.

Sources: Edmund Yong, Official Docs

What it does Wipes the entire conversation context and starts fresh while staying in the same terminal session.

Why it matters Old context bleeds into new tasks. If you just finished a database migration and now want to build a UI component, the database context pollutes Claude's thinking. /clear wipes. /compact summarizes. Know the difference.

Sources: Jaymin West, Official Docs

What it does Tells Claude exactly which tool, file, or approach to use instead of letting it guess.

Why it matters "Explore the codebase" is vague. "Read src/api/routes.ts and src/db/schema.ts, then propose changes" is precise. Explicit instructions remove randomness and reduce wasted tool calls.

Sources: Academind, Jaymin West

What it does Commit before every major Claude task so you have reliable recovery points.

Why it matters Claude can make sweeping changes across dozens of files. /rewind exists but is less reliable than git. A quick commit before asking Claude to refactor gives you a guaranteed rollback point.

Sources: Academind, Official Docs

What it does Save repeating prompts as .claude/commands/*.md files and call them with /command-name from any session.

Why it matters If you type the same prompt more than twice, it should be a command. Commands ensure consistency, reduce typing, and compound over time.

"My 10 most-used commands replaced 6 hours of weekly work."

Sources: John Kim, Official Docs

What it does Every active MCP server adds its tool definitions to every single Claude call, consuming tokens even when unused.

Why it matters A single MCP with 50 tools can add thousands of tokens per request. Scope MCPs per-directory in settings.json so they only load when relevant.

"I try very hard not to use MCPs because they blow up context."

Sources: Edmund Yong, Jaymin West

What it does Shows a detailed breakdown of where your context tokens are being spent: system prompt, CLAUDE.md, MCPs, conversation history.

Why it matters Most engineers never check where their tokens go. MCPs are usually the biggest offenders, sometimes consuming 30-50% of available context with tool definitions alone. You can't optimize what you don't measure.

Sources: Edmund Yong

What it does When connecting integration platforms, expose only the specific actions you need instead of loading the entire catalog.

Why it matters Zapier exposes 8,000+ actions by default. Each one becomes a tool definition in your context. That's potentially hundreds of thousands of wasted tokens. Pick 5-10 actions and skip the rest.

Sources: Edmund Yong

What it does Define subagents by specific tasks they perform, not vague roles they fill.

Why it matters "Frontend developer agent" is useless: it's a role without boundaries. "UI reviewer, which uses Playwright to screenshot components, compares against design spec, reports mismatches" is a task with clear inputs, outputs, and tools. Task-scoped agents work. Role-scoped agents hallucinate.

Sources: Official Docs, John Kim

What it does Setting isolation to "worktree" gives each agent its own git worktree, a full copy of the repo that doesn't conflict with your working directory.

Why it matters Without worktrees, two Claude instances editing the same repo create file conflicts. With worktrees, each agent works in isolation. Perfect for parallel code review, testing, or feature branches.

Sources: Official Docs

What it does Rules in .claude/rules/ can specify glob patterns so they only load when Claude touches matching files.

Why it matters Your React component conventions are irrelevant when Claude is editing a database migration. Path-scoped rules keep context lean by only loading relevant instructions.

Sources: John Kim, Official Docs

What it does Forces Claude to return output matching a strict JSON schema, parsing unstructured text into structured data.

Why it matters When you need machine-readable output (for CI pipelines, data processing, or chaining commands), JSON schema guarantees the shape. No more regex parsing of Claude's prose.

Sources: Official Docs

What it does Use claude -p (headless mode) in GitHub Actions, pre-commit hooks, and build pipelines to automate code quality checks.

Why it matters Claude becomes a quality gate in your pipeline. Every PR gets an AI review. Every commit gets checked against your conventions. AI quality gates catch issues that linters miss.

"Build script with AI quality gate."

Sources: Academind, Official Docs

What it does Multiple Claude instances coordinating on a shared task list with dependencies, running in parallel.

Why it matters One agent writes the backend API. Another builds the frontend components. A third writes tests. They work simultaneously, aware of each other's progress. Best for parallel review and independent workstreams.

Sources: Official Docs

What it does Setting memory: user in agent frontmatter lets the agent read and write a MEMORY.md file that persists across sessions.

Why it matters Without memory, every session starts cold. With persistent memory, agents accumulate knowledge: client names, past bugs, preferred patterns, things that failed before. Compound intelligence across sessions.

Sources: Official Docs

What it does PreToolUse hooks intercept dangerous operations before they execute. PostToolUse hooks run automated checks after every edit.

Why it matters A PreToolUse hook can block Claude from deleting production config files. A PostToolUse hook can run ESLint after every file edit. Shell scripts as automated quality gates. No human intervention needed.

Sources: Official Docs, John Kim

What it does A git-controlled markdown vault with CLAUDE.md, custom skills, agents, and commands that functions as a full business operating system.

Why it matters Claude Code isn't just a coding assistant. When you combine a structured knowledge base + CLAUDE.md + skills + agents + commands, you get a system that handles sales, content, client work, operations, and engineering. The compound effect is massive.

"Not a coding assistant. An operating system."

Sources: Original research, 800+ hours usage

What it does Skills bundle instructions (SKILL.md), reference data, and scripts into self-contained workflow packages that Claude loads on demand.

Why it matters MCPs are for external API connections: databases, email, calendar. Skills are for your own processes: how you write proposals, how you research prospects, how you generate content. They don't burn context like MCPs do.

Sources: Original research, Official Docs

What it does Combines build + test + lint commands in CLAUDE.md with Playwright visual testing to create a fully autonomous quality loop.

Why it matters Build and test catch logic errors. Lint catches style issues. But neither catches visual bugs. Adding Playwright screenshots gives Claude 'eyes.' It can see what it built, compare against expectations, and self-correct visual issues without human review.

Sources: Edmund Yong, John Kim

What it does The deliberate practice of controlling what information enters Claude's context window and when.

Why it matters Prompt engineering is writing good instructions. Context engineering is controlling the entire information environment. The engineers who master this work 5-10x faster than those who just write good prompts. Context is the bottleneck, not the model.

"What you put in context matters more than what you prompt."

Sources: Edmund Yong, John Kim, Official Docs

The Efficiency Ladder

Each level compounds on the previous one

Quick Reference

All 25 tips at a glance

Start with Level 1. Master it. Then unlock Level 2.

Install Claude Code and start building.

don't miss what's next.

playbooks, templates, and tools that actually save you hours. straight to your inbox. no spam. unsubscribe anytime.

Want this running in your business, not just your terminal? Our Claude Code development agency ships it for you, or book a free consultation to scope your setup.

Day 30: The Master Test (30 Questions)

Day 32: The Claude Code Playbook