Claude / Claude Code learning paths
Choose ordered beginner and professional Claude / Claude Code tutorials for practical software engineering.
- Author
- absequ
- Published
- Updated
- Category
- AI Tools
- AI Tools
- Claude / Claude Code
- tool overview
Start here to choose an ordered learning path for Claude / Claude Code. Basic programming is assumed; prior knowledge of this specific tool is not. Each path has six substantive chapters and includes prerequisites, practice tasks, expected results and troubleshooting.
On this page
Choose your learning path
Claude conversational interfaces and Claude Code serve different workflows. A chat can help reason about supplied code; Claude Code can act on repository files and development tools. This collection teaches the terminal agent first, then explains project guidance, extensions and managed-team boundaries. Supported IDE, desktop and browser workflows depend on access and provider configuration.
Use Getting Started first if you have not completed a small edit–test–review task with this tool. Choose Professional Engineering after you can inspect a diff, preserve user changes and explain what a focused test does and does not prove.
- Use a disposable notes project and synthetic data for exercises. Do not use employer credentials or production infrastructure.
- Check account entitlement and data-handling policy before supplying a repository. Tool access does not authorize every possible action.
- Commands in these articles are teaching examples. Follow the target repository package manager and validation rules when transferring the workflow.
Getting Started & Core Workflows
Read these six chapters in order. No prior use of this tool is needed.
- Distinguish Claude chat from Claude Code
- Install Claude Code and verify account access
- Create a tested function through an explicit task contract
- Trace an unfamiliar repository using targeted context
- Plan and implement a small feature with tool approvals
- Reproduce a bug and recover from an incorrect edit
Professional Engineering Workflows
Read these six chapters in order. Prerequisite: the core path or equivalent demonstrated experience.
- Write CLAUDE.md guidance and stage a large task
- Deliver a React-to-service feature with explicit contracts
- Choose unit and integration tests that expose real defects
- Review diffs, protect secrets and prepare a pull request
- Use skills, subagents, hooks and MCP deliberately
- Run bounded automation and control team usage
Access, verification and next steps
Official references were checked on 2026-11-06. Pricing, model lists and quotas are deliberately not fixed here. If a documented feature is unavailable, check platform/version, account eligibility, organization settings and the current reference before trying alternate flags or installing extensions.
A finished AI task means a reviewed result with relevant evidence. The exercises do not claim production deployment, enterprise compliance or provider correctness from a unit test. Use the existing project checks and record deferred validation. Advanced topics fit the professional path; no arbitrarily numbered seasons or empty future chapters are published.
References
Claude Code overview — Anthropic
Claude Code setup — Anthropic