Efficiency Hacks

The developer who saves 10 minutes per task does not seem impressive. But across 30 tasks per day, that is 5 hours per week. These efficiency hacks are the small techniques that compound into massive productivity gains.

What You Will Walk Away With

• Context management techniques that keep sessions lean and fast
• Output format tricks for different workflows
• Shell aliases and functions that reduce keystrokes
• Patterns for avoiding common time sinks

Context Management

Clear Between Unrelated Tasks

The single biggest efficiency win is clearing context when switching tasks:

/rename payment-bug-investigation
/clear

Stale context from a previous task makes every subsequent message more expensive (more tokens processed) and less accurate (Claude uses irrelevant context).

Targeted Compaction

When you need to stay in the same session but context is bloated:

/compact Keep: file paths I edited, test results, error traces. Remove: exploratory file reads, discussion about alternatives, my questions.

Add Compaction Rules to CLAUDE.md

# Compact instructions
When compacting, preserve:
- Test results and error output
- File paths and code changes made
- Key decisions and their rationale

Remove:
- Exploratory file reads that did not lead to changes
- Verbose command output that has been summarized
- Discussion of rejected approaches

Shell Aliases and Functions

Quick Claude Code Shortcuts

Add to ~/.zshrc or ~/.bashrc:

# Quick question -- ask Claude without starting a session
alias cq='claude -p'

# Continue last session
alias cc='claude -c'

# Review current changes
alias cr='git diff | claude -p "Quick review: only flag CRITICAL and HIGH issues."'

# Explain a file
explain() {
  claude -p "Explain what $1 does, its key functions, and how it fits into the project."
}

# Generate tests for a file
gentest() {
  claude -p "Generate comprehensive tests for $1. Follow existing test patterns in this project."
}

# Debug an error
debug() {
  echo "$@" | claude -p "Analyze this error and suggest a fix. Read the relevant source files."
}

Tip

Copy-paste shell aliases for daily Claude Code use:

# Add to ~/.zshrc or ~/.bashrc

# Quick operations
alias cq='claude -p'           # Quick question
alias cc='claude -c'            # Continue last session
alias cr='git diff | claude -p "Review: flag only CRITICAL issues"'

# Resume named sessions
alias cdev='claude -r dev-session'
alias cdebug='claude -r debug-session'

# Pipe helpers
alias clog='claude -p "Summarize these logs. Highlight errors and warnings."'
alias cdiff='claude -p "Explain what these changes do and flag any issues."'

Output Format Tricks

JSON for Script Consumption

When you need structured output:

claude -p "List all API endpoints with their HTTP method, path, and handler file" \
  --output-format json | jq '.result'

Structured Output with JSON Schema

For guaranteed output structure:

claude -p "Analyze the test coverage of src/api/" \
  --json-schema '{"type":"object","properties":{"total_files":{"type":"number"},"covered_files":{"type":"number"},"uncovered_files":{"type":"array","items":{"type":"string"}}}}'

Common Time Sinks and How to Avoid Them

”Let Me Read Everything First”

Claude’s default behavior is to read many files before acting. For focused tasks, constrain the scope:

Fix the null pointer in src/api/users.ts line 42.
Only read src/api/users.ts and its direct imports.
Do not explore other files.

“Let Me Summarize What I Did”

Claude often spends tokens summarizing changes after making them. Add to your CLAUDE.md:

After making changes, do not provide a summary unless I ask for one.
Instead, just show the git diff of what changed.

Running Full Test Suites After Every Change

# In CLAUDE.md
When running tests after a change, run only the tests related to the modified file.
Use: npx jest [file] --no-coverage
Only run the full test suite when I ask for it or before committing.

Reading Package-Lock or Generated Files

# In CLAUDE.md
Never read these files:
- package-lock.json
- yarn.lock
- any file in dist/ or build/
- any file in node_modules/
- any .map file

Quick Wins

Use --add-dir for Multi-Repo Work

# Work on a frontend app with access to the shared library
claude --add-dir ../shared-components

Fallback Model for Overloaded Periods

claude -p "Quick task" --fallback-model sonnet

If Opus is overloaded, this automatically falls back to Sonnet instead of failing.

PR-Linked Sessions

# Create a session linked to a PR
claude --from-pr 123

This loads context from the PR, making it easy to address review comments.

Tip

Copy-paste CLAUDE.md efficiency rules:

# Efficiency Rules

- Do not summarize changes after making them
- Run only related tests after changes, not the full suite
- Never read generated files (dist/, build/, node_modules/, *.lock)
- Use grep to find specific content before reading entire files
- Prefer targeted file reads over directory scans
- When I say "fix it," apply the fix and run the relevant tests without asking for confirmation

When This Breaks

Aliases conflict with other tools: Check for name conflicts with which cq before adding aliases. Choose unique names that do not shadow existing commands.

Context gets cleared accidentally: Get in the habit of using /rename before /clear. Sessions persist even after clearing, so you can resume them later.

Efficiency rules in CLAUDE.md are too restrictive: If Claude seems unable to explore when needed, use “ignore efficiency rules for this task” to override temporarily. The rules are guidance, not hard blocks.

What is Next

• Terminal Mastery — Deeper terminal optimization
• Monitoring and Costs — Track the impact of your efficiency improvements
• Setup and Configuration Tips — More configuration optimizations