DEV Community

Cover image for Getting Started with Claude Code (Super Easy!)
Daniel Shashko
Daniel Shashko

Posted on

Getting Started with Claude Code (Super Easy!)

#tutorial #cli #ai #tooling

Let's get you up and running with Claude Code in a few minutes. This AI-powered coding assistant will feel like having a smart colleague right in your terminal.

What you'll need

Before we start, make sure you've got:

  • A terminal or command prompt open
  • A code project to work with (any project is fine)
  • A Claude.ai or Claude Console account

Claude.ai is probably your best bet if you're just getting started since it has subscription plans that are easier to manage.

Installing Claude Code

Pick the method that works for your system:

macOS or Linux with Homebrew:

brew install --cask claude-code
Enter fullscreen mode Exit fullscreen mode

macOS, Linux, or WSL:

curl -fsSL https://claude.ai/install.sh | bash
Enter fullscreen mode Exit fullscreen mode

Windows PowerShell:

irm https://claude.ai/install.ps1 | iex
Enter fullscreen mode Exit fullscreen mode

Windows Command Prompt:

curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
Enter fullscreen mode Exit fullscreen mode

Logging in

Once Claude Code is installed, you'll need to sign in. Start an interactive session and it'll walk you through the login process:

claude
# You'll get prompted to log in on first use
Enter fullscreen mode Exit fullscreen mode

If you need to log in manually or switch accounts later, just use:

/login
Enter fullscreen mode Exit fullscreen mode

You can use either a Claude.ai account (the subscription one) or a Claude Console account (pay-per-use with API credits). Both work fine, and you can even have both under the same email if needed.

When you first connect a Claude Console account, Claude automatically creates a workspace called "Claude Code" for tracking your usage and costs. Pretty handy for keeping tabs on what you're spending.

Once you're logged in, your credentials get saved locally so you won't have to do this dance every time.

Your first session

Navigate to any project directory and fire up Claude Code:

cd /path/to/your/project
claude
Enter fullscreen mode Exit fullscreen mode

You'll see a welcome screen with your session info, recent conversations, and any updates. Type /help to see what commands are available, or /resume to pick up where you left off in a previous conversation.

Understanding your codebase

Let's start by having Claude take a look at your project. Try asking:

> what does this project do?
Enter fullscreen mode Exit fullscreen mode

Claude will scan through your files and give you a summary. You can get more specific too:

> what technologies does this project use?
> where is the main entry point?
> explain the folder structure
Enter fullscreen mode Exit fullscreen mode

You can also ask Claude about itself:

> what can Claude Code do?
> how do I use slash commands in Claude Code?
> can Claude Code work with Docker?
Enter fullscreen mode Exit fullscreen mode

The cool thing is that Claude reads your files automatically as it needs them. You don't have to manually feed it context like you would with some other AI tools. It also knows about its own documentation, so it can answer questions about its features.

Making your first code change

Time for the fun part. Let's have Claude actually write some code:

> add a hello world function to the main file
Enter fullscreen mode Exit fullscreen mode

Here's what happens next:

  1. Claude finds the right file to modify
  2. Shows you exactly what it wants to change
  3. Asks for your permission
  4. Makes the edit once you approve

Claude always asks before touching your files. You can approve changes one by one, or if you're feeling confident, enable "Accept all" mode for the session.

Working with Git

Claude makes Git operations feel natural. Instead of remembering commands, just describe what you want:

> what files have I changed?
> commit my changes with a descriptive message
> create a new branch called feature/quickstart
> show me the last 5 commits
> help me resolve merge conflicts
Enter fullscreen mode Exit fullscreen mode

It's like having a Git expert sitting next to you who actually pays attention to what you're working on.

Fixing bugs and adding features

This is where Claude really shines. Describe what you want in plain English:

> add input validation to the user registration form
> there's a bug where users can submit empty forms - fix it
> refactor the authentication module to use async/await instead of callbacks
> write unit tests for the calculator functions
Enter fullscreen mode Exit fullscreen mode

Claude will figure out where the relevant code lives, understand the context, implement a solution, and even run tests if you have them set up.

Other useful workflows

Here are some other things you can try:

Code review:

> review my changes and suggest improvements
Enter fullscreen mode Exit fullscreen mode

Documentation:

> update the README with installation instructions
Enter fullscreen mode Exit fullscreen mode

Testing:

> write integration tests for the API endpoints
Enter fullscreen mode Exit fullscreen mode

The key is to talk to Claude like you would a helpful colleague. Be conversational and describe what you're trying to achieve.

Essential commands you'll use daily

Command What it does
claude Start interactive mode
claude "task" Run a one-time task and exit
claude -p "query" Ask a quick question and exit
claude -c Continue your most recent conversation
claude commit Create a Git commit
/help Show available commands
exit or Ctrl+C Exit Claude Code

Tips that'll save you time

Be specific with your requests. Instead of "fix the bug," try "fix the login bug where users see a blank screen after entering wrong credentials." The more context you give Claude, the better it can help.

Break complex tasks into steps. Don't try to do everything at once:

> 1. create a new database table for user profiles
> 2. create an API endpoint to get and update user profiles  
> 3. build a webpage that allows users to see and edit their information
Enter fullscreen mode Exit fullscreen mode

Let Claude explore before making changes. Have it understand your codebase first:

> analyze the database schema
> build a dashboard showing products that are most frequently returned by our UK customers
Enter fullscreen mode Exit fullscreen mode

Learn the shortcuts. Press ? to see keyboard shortcuts, use Tab for command completion, press ↑ for command history, and type / to see all slash commands.

What's next?

Now that you've got the basics down, you can explore more advanced features in the documentation. The CLI reference has all the commands, the configuration guide shows you how to customize things, and the common workflows section walks through more complex tasks.

If you get stuck, just type /help in Claude Code or ask "how do I..." Claude's pretty good at explaining its own features. You can also check out the community Discord for tips and support from other developers.

The main thing to remember is that Claude Code is designed to be conversational. Don't overthink it - just describe what you want to accomplish and let it help you get there.

Top comments (0)