Starting with Claude Code can feel overwhelming with its many features. This beginner-friendly guide walks you through the essential setup steps: installing the CLI, creating your first CLAUDE.md, configuring permissions, and running your first AI-assisted coding session. By the end, you will have a well-configured project that maximizes Claude Code's effectiveness.
setupbeginnerCLAUDE.mdpermissionsonboarding
Installation and Authentication
Claude Code is installed as a global npm package. After installation, you authenticate with your Anthropic account. The CLI stores your credentials securely and manages sessions automatically.
Once authenticated, navigate to your project directory and run 'claude' to start an interactive session. Claude Code automatically detects your project structure, reads package.json, and understands your tech stack without any configuration.
For team environments, consider using environment variables for authentication so that CI/CD pipelines and shared development machines can use Claude Code without manual login steps.
# Install Claude Code globally
npm install -g @anthropic-ai/claude-code
# Authenticate (opens browser)
claude auth login
# Start your first session
cd ~/my-project
claude
# Verify installation
claude --version
Creating Your CLAUDE.md
CLAUDE.md is the single most important file for Claude Code productivity. It acts as persistent instructions that Claude reads at the start of every session. Think of it as onboarding documentation for your AI pair programmer.
Start minimal. A good CLAUDE.md answers three questions: What is this project? What tech stack does it use? What conventions should Claude follow? Resist the urge to write a comprehensive document on day one. Instead, add rules organically as you discover patterns.
Place CLAUDE.md at the project root. Claude Code searches for it automatically. You can also create a ~/.claude/CLAUDE.md for global instructions that apply to all projects.
# CLAUDE.md
## Project
E-commerce API built with Node.js + Express + PostgreSQL.
## Stack
- Runtime: Node.js 20
- Framework: Express 4
- Database: PostgreSQL 16 + Prisma ORM
- Testing: Vitest
- Linting: ESLint + Prettier
## Conventions
- Use async/await, never raw promises
- All API responses follow { data, error, meta } shape
- Database queries go through Prisma, no raw SQL
- Tests are co-located: foo.ts → foo.test.ts
Permission Configuration
Claude Code uses a permission model to control which actions it can take autonomously. By default, it asks for confirmation before running shell commands, editing files, or making network requests. This is safe but can slow you down.
For trusted projects, you can pre-approve specific actions. The three permission modes are: ask (default), auto-approve for read-only operations, and full auto-approve. Most developers start with the default and gradually allow more as they build trust.
You can also configure per-tool permissions. For example, you might allow file edits automatically but require confirmation for git operations. This granular control lets you balance speed with safety.
# Check current permission settings
claude config list
# Allow file reads without confirmation
claude config set autoApprove.read true
# Allow file edits in specific directories
claude config set autoApprove.editPaths "src/**,tests/**"
# In CLAUDE.md, set project-level permissions
# These apply only to this project:
# Allow: Read, Edit, Glob, Grep
# Ask: Bash, Write (new files)
Your First Coding Session
With setup complete, it is time to do real work. Start with a small, well-defined task to build confidence. Good first tasks include: adding a utility function, writing tests for existing code, or fixing a known bug.
Be specific in your prompts. Instead of 'make the code better,' say 'add input validation to the createUser endpoint in src/routes/users.ts.' Specific prompts produce better results and consume fewer tokens.
After each session, review what Claude did. Check the git diff, run your tests, and note any patterns you want to encode into CLAUDE.md for future sessions. This feedback loop is how you progressively make Claude Code more effective for your specific project.
# Good first tasks - specific and scoped
claude "add a validateEmail utility in src/utils/validators.ts with tests"
claude "fix the null pointer in src/services/user.ts line 47"
claude "add JSDoc comments to all exported functions in src/utils/"
# Review what changed
git diff
npm test
# If something went wrong, undo easily
git checkout -- .
Terminal Preview
Your First Claude Code Project
About Your First Claude Code Project
Claude Code guides provide in-depth, step-by-step instructions for mastering specific aspects of Claude Code. Your First Claude Code Project is a Beginner-level guide that walks you through best practices, real-world techniques, and practical tips to help you get the most out of Claude Code in your daily workflow.