The Quick Answer

To get started, just follow the commands below in favorite terminal. You'll need to have Node.js 18 or newer first.

# Install Claude Code globally
$npm install -g @anthropic-ai/claude-code
 
# Navigate to your project directory
$cd /path/to/your/project
 
# Start Claude Code
$claude
 
# Initialize your project context
$/init

Think of Claude as a fast intern. That means: be specific, review outputs, and update CLAUDE.md when it learns your preferences.

Essential Commands

Below are some essential commands to get you started using Claude Code and to keep you productive. There are many, many more commands that you can find in other guides.

Project Setup Commands

/init - Analyzes your codebase and creates a CLAUDE.md file with project context. Run this first in any new project.

/ide - Connects to your IDE to see open files and linter warnings. Supports VS Code, Cursor, and JetBrains IDEs.

/terminal-setup - Configures your terminal for optimal Claude Code experience (enables Shift+Enter for newlines).

/model - Switch between Claude models (only Sonnet, only Opus, or a combo) during your session.

/add-dir - Add additional working directories to your project scope. Useful for monorepos or related projects.

/config - View or modify your Claude Code configuration settings.

/permissions - Manage file access permissions for Claude Code. Review what Claude can read and modify.

Development Commands

Instead of complex git commands, use natural language:

$> Create a commit with all the user auth changes

Instead of manual refactoring:

$> Update all components to use the new theme system

Instead of searching documentation:

$> How do I set up database migrations in this project?

Daily Use Commands

/review - Request a comprehensive code review of your changes. Claude analyzes for bugs, performance, and best practices.

/compact - Compact long conversations to save context. Optionally focus on specific topics.

/cost - Check your token usage and estimated costs for the current session.

/clear - Clear conversation history when starting a new task.

/vim - Enter vim mode for advanced text editing with familiar keybindings.

# prefix - Start any message with # to save it to CLAUDE.md.

Keyboard Shortcuts:

• Ctrl+C - Cancel current generation
• Ctrl+D - Exit Claude Code
• Esc + Esc - Edit your previous message
• Ctrl+L - Clear terminal screen

Session Management

Resume Last Session

$claude --resume

Picks up exactly where you left off with full context.

List Past Sessions

$claude --list-sessions

Jump back into any previous project conversation.

Common Beginner Mistakes to Avoid

1. Treating Claude Like a Search Engine

❌ Wrong: "How to create React component"

✅ Right: "Create a UserProfile component that displays name, avatar, and bio from our user API"

2. Skipping the Planning Phase

❌ Wrong: Immediately asking for code implementation

✅ Right: "Let's plan how to add user authentication. Don't write code yet, just outline the approach."

Or, you can use planning mode by pressing Shift+Tab twice.

Power User Tips (Save Hours Per Week)

1. Stage Changes Frequently

Before major refactoring:

$git add .

Creates restore points if you need to rollback.

2. Use the Hash Prefix for Memory

> # Our API uses snake_case for all endpoints

Claude asks if you want to save this to CLAUDE.md for future reference.

3. Interrupt and Course-Correct

• Escape - Interrupt Claude mid-action to redirect
• Double Escape - Jump back in history to try a different approach

4. Parallel Development

Open multiple terminals with Claude Code for different features.

5. Custom Commands

Create .claude/commands/review.md:

Review the file at $ARGUMENTS for:
- Security issues
- Performance problems  
- Code style violations

Now use:

$> /review src/auth.js

Quick Workflow Examples

Legacy Code Migration

$> Analyze this codebase and create a migration plan from JavaScript to TypeScript

Then progressively:

$> Convert the auth module to TypeScript with proper types

Automated PR Reviews

$cat pr-comments.txt | claude -p "Address these review comments and update the code"

Complex Debugging

> Here's the error log: [paste]. Find the root cause and suggest fixes