Claude Code / quick start
Claude Code Quick Start
Install Claude Code, enter the project root directory, let it read the code first, and then gradually approve modifications and commands.
Install and start
The point of getting started quickly is to get Claude Code running on a real but low-risk project first. After installation, enter the project root directory to start so that it can see the repository files, Git status and project commands.
It is recommended for first-time users to start by "explaining the codebase" rather than overhauling it directly. This confirms that Claude understands the project structure, entry points, run commands, and test workflow first.
npm install -g @anthropic-ai/claude-code
cd your-awesome-project
claudeThe first prompt
A good prompt should tell Claude to read first, explain first, and plan first. Think of it like onboarding a new colleague, not a one-time code generator.
- Let Claude output the understanding first, and then let him modify it.
- Give acceptance criteria, such as build/test/lint or browser validation.
- At the end of each task, it is required to explain what has been changed, how to verify it, and what risks there are.
I just took over this code base. Please don't change the file yet.
Please explain:
1. Main entrance of the project
2. Run the command locally
3. Test and build commands
4. The most error-prone module
5. If you want to fix a bug, where to start?Understanding permission prompts
Claude Code may request permission when editing files, running commands, or using the network. It is recommended to keep the default or plan mode during the quick start phase, and not to start by bypassing permissions.
default
Ideal for entry-level and sensitive projects. Claude reads mainly and prompts before key actions.
acceptEdits
Ideal if you prefer to review diffs collectively rather than approving file edits one by one.
plan
It is suitable to explore and decide on the plan first, and then allow code changes after confirmation.
Verify after completion
Don’t just accept Claude’s textual summary. At least look at the diff, run the command, inspect the page or test the output.
git diff
pnpm build
pnpm test
# The front-end page also needs to open the browser to check the real interaction.Complete usage points
Supplement the core concepts, operation sequences, permission boundaries and verification requirements that are easily compressed and missed in official documents, making it easier for English readers to learn completely by page.
Quickly start the complete process
The Quick Start page focuses on everything from installation to your first high-quality task. After installing the CLI, go to the project root directory and start Claude. Don't ask for modifications directly the first time, but let Claude explain the project.
- Install and log in to Claude Code.
- Enter the real project root directory.
- Ask about the project structure, running commands, test commands and key modules.
- Give a small task, clarify the scope and acceptance criteria.
- Check the cause and effect when editing or command approval.
- When finished look at the diff, run the verification and ask for a risk statement.
The most important habits for novices are: let Claude read and explain first, and then let him change it; let him plan it first, and then approve the execution; see verification first, and then consider submission.
Study Checklist
Put the content on this page into real tasks and use the five dimensions of entry, context, permissions, verification and team rules to check whether you have truly mastered it.
Study Checklist
After reading this page, do not just remember the concept name. You should be able to place "Claude Code Quick Start" back into a real Claude Code engineering workflow: where the task starts, what context the system loads, which actions need approval, how the result is verified, and how to roll back when it fails.
If this is a concept page, be specific about how it affects the real task: does it change context, permissions, execution paths, validation methods, or changes the team collaboration process.
- Be able to describe in your own words the specific problem this page solves, rather than just reciting the title.
- Able to write a minimal example task with goals, scope, prohibitions, and acceptance criteria.
- Be able to determine which information should be put into the current prompt and which should be captured as project rules or configurations.
- Be able to explain which long-term rules should go into CLAUDE.md, and which runtime behavior should be handled by settings, permissions, Hooks, Skills and MCP.
- Ability to check diffs, command output, test results, screenshots or PR notes after a task is completed instead of just trusting the natural language summary.
If this page is used for team training, ask learners to complete a small task with Claude Code: read and explain first, submit a plan, make the smallest useful change, and close with real verification commands plus human diff review.