The terminal interface is Claude Code’s primary interaction method, and mastering it transforms your development speed. These 10 tips cover essential commands, keyboard shortcuts, and productivity techniques that power users rely on daily.
Understanding Claude Code’s command structure enables fluid interaction:
# Start interactive sessionclaude
# Run one-time taskclaude "implement user authentication with JWT"
# Quick query with immediate exitclaude -p "explain this regex: /^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$/"
# Continue most recent conversationclaude -c
# Resume specific previous conversationclaude -r# Skip permissions for faster workflowclaude --dangerously-skip-permissions
# Add multiple directoriesclaude --add-dir ../backend --add-dir ../frontend
# Use specific modelclaude --model sonnet # or claude --model claude-sonnet-4-20250514
# Debug mode for troubleshootingclaude --verbose --debug# JSON output for automationclaude -p "analyze security vulnerabilities" --output-format stream-json
# Pipe output to other toolsclaude -p "generate test cases" | jq '.content'
# Use in scriptsresult=$(claude -p "format this JSON" < data.json)echo "$result"Quick Reference
-p, --print: Run single prompt and exit (non-interactive)-c, --continue: Continue last conversation-r, --resume: Resume from history-m, --model: Specify model to use-v, --verbose: Show debug information--add-dir: Include additional directoriesSlash commands provide quick access to Claude Code’s features:
Essential Slash Commands:
/help - Show all available commands and usage/init - Initialize project with CLAUDE.md/review - Request comprehensive code review/clear - Clear conversation history/config - View or modify configuration/status - View account and system status/memory - Edit CLAUDE.md memory files/permissions - Manage tool permissions/cost - Check token usage and costs/compact - Compress conversation history/add-dir - Add directory to workspace/hooks - Configure automation hooks/terminal-setup - Configure terminal settings/ide - Connect to IDE for diagnostics/install-github-app - Enable GitHub integrationCustom command examples:
# Create custom test commandecho 'Generate comprehensive tests for: $ARGUMENTS' > .claude/commands/test.md
# Use it/test UserService.js
# Create deployment commandecho 'Deploy to staging following our process: $ARGUMENTS' > .claude/commands/deploy-staging.md
# Use it/deploy-staging --version 2.1.0One of the most impactful habits for Claude Code efficiency:
# Clear at the start of each new task/clear
# Why this matters:# 1. Saves tokens (no history to process)# 2. Prevents context confusion# 3. Avoids compaction overhead# 4. Faster response times# 5. Cleaner mental modelWhen to Clear
Best practices for context management:
# Good workflowclaude/clear# Work on authentication feature# Complete authentication
/clear# Work on payment integration# Complete payment integration
# Bad workflowclaude# Work on authentication# Work on payment without clearing# Work on UI without clearing# Context becomes muddledClaude Code maintains comprehensive history across sessions:
# Navigate with arrow keys↑ # Previous command↓ # Next command
# Access full historyclaude -r# Shows numbered list of previous conversations
# Jump to specific conversationclaude -r 5# Resumes conversation #5
# Search historyclaude --history | grep "authentication"# Find all conversations about authentication# During a session↑ ↑ ↑ # Go back through promptsEscape Escape # Show message list5 # Jump to message 5
# Between sessionsclaude -r # List all sessionsclaude -r 12 # Resume session 12claude -c # Continue last session# Export conversationclaude --export > conversation.md
# Clear all historyclaude --clear-history
# Archive old conversationsclaude --archive --before "2024-01-01"Efficient file referencing is crucial for providing context:
Using @ mentions
Refactor @UserService.js to use dependency injectionUpdate @components/Button.tsx to support dark modeDrag and drop with Shift
Glob patterns
Review all test files: @**/*.test.jsUpdate all React components: @components/**/*.tsxMultiple file references
Ensure consistency between @User.model.js, @user.service.js, and @user.controller.jsClaude Code excels at understanding intent without specific syntax:
Instead of memorizing commands, just describe what you want:
"Fix the bug in user authentication""Add comprehensive tests for the payment module""Refactor this function to be more readable""Help me understand how the caching layer works""Create a new feature for exporting data to CSV""Review my code for security vulnerabilities""Optimize this query that's running slowly""Update the documentation for the API endpoints"Natural Language Patterns
Claude Code understands:
Examples of natural language understanding:
# Vague request → Claude asks clarifying questions"Make this faster"> I see you want to improve performance. Could you specify:> 1. Which part is slow?> 2. What's the current performance?> 3. What's your target?
# Context-aware request"Do the same thing for the product service"> I'll apply the same dependency injection pattern I used> for UserService to the ProductService
# Implicit requirements"Make this production ready"> I'll add:> - Error handling> - Input validation> - Logging> - Tests> - DocumentationClaude Code provides sophisticated git integration:
# Status and changes"What files have I changed?""Show me the git diff""What's on the staging area?"
# Committing"Commit my changes with a descriptive message""Create a commit following conventional commits""Amend the last commit"
# Branches"Create a new branch called feature/user-auth""Switch to the main branch""Show me all branches"# Complex operations"Help me resolve these merge conflicts""Cherry-pick the auth fixes from develop""Rebase my feature branch on main""Squash the last 3 commits"
# History and analysis"Show me who last modified this function""Find when this bug was introduced""Generate a changelog from git history"
# Workflow automation"Create a PR with a detailed description""Update the PR based on review comments"Essential keyboard shortcuts for productivity:
Universal Shortcuts:- Escape - Stop current operation (not exit)- Escape Escape - Show message navigation- Tab - Command/file completion- Shift+Enter - New line in prompt (after setup)- Ctrl+C - Exit Claude Code- Ctrl+L - Clear screen- Ctrl+R - Search command history
File Operations:- Ctrl+V - Paste image (not Cmd+V on Mac)- Shift+Drag - Reference file (not open)
Navigation:- ↑/↓ - Navigate command history- Page Up/Down - Scroll through output- Home/End - Jump to start/end
Special:- # - Quick CLAUDE.md update- / - Start slash command- @ - Start file referencePlatform Differences
Perfect for automation and quick operations:
# Quick formattingclaude "format this SQL query" < query.sql > formatted.sql
# Code reviewclaude "review this PR for security issues" < pr.diff
# Documentation generationclaude "generate JSDoc comments" < utils.js > documented.js
# Batch operationsfor file in *.js; do claude "add error handling" < "$file" > "safe_$file"done
# Pipeline integrationgit diff | claude -p "explain these changes" | tee explanation.md
# Automated testingclaude "write tests for this function" < service.js > service.test.jsIntegration examples:
# Git hooksfiles=$(git diff --cached --name-only --diff-filter=ACM | grep '\.js$')for file in $files; do claude "check for console.log statements" < "$file"done
# CI/CD pipeline# .github/workflows/review.yml- name: Claude Review run: | claude "review for performance issues" < src/Extend Claude Code with project-specific commands:
Create command directory
mkdir -p .claude/commandsCreate command file
Create a new feature with our standard structure:
Feature name: $ARGUMENTS
1. Create feature branch2. Set up folder structure: - /features/$ARGUMENTS/ - /features/$ARGUMENTS/components/ - /features/$ARGUMENTS/hooks/ - /features/$ARGUMENTS/tests/3. Create index files with exports4. Add to main router5. Create basic test setupUse the command
/feature user-profileCreate nested commands
mkdir -p .claude/commands/db# Now use: /db/migrateAdvanced command examples:
Perform comprehensive code review:- Security vulnerabilities- Performance issues- Code style violations- Missing tests- Documentation gaps
Focus on: $ARGUMENTS
# .claude/commands/refactor.mdRefactor following our patterns:- Extract constants- Add type safety- Improve naming- Reduce complexity- Add error handling
Target: $ARGUMENTS
# .claude/commands/test/integration.mdCreate integration tests for: $ARGUMENTS- Use our test utilities- Mock external services- Test error scenarios- Verify response formatCommand Best Practices
Combining these command-line techniques creates a powerful workflow:
# Start freshclaude --dangerously-skip-permissions/clear
# Set up workspace/add-dir ../shared/add-dir ../backend
# Quick task"Create user authentication with JWT"
# Review and test/review"Add comprehensive tests"
# Natural git workflow"Commit these changes""Create a PR"
# Jump to previous workEscape Escape3 # Jump to message about database schema
# Quick check/cost # Monitor token usage
# Continue tomorrowclaude -c # Pick up where you left offWith command-line mastery achieved, you’re ready to tackle large, complex codebases. Continue to Large Codebase Management to learn strategies for enterprise-scale development.