Practical Claude Code course

Claude Code course for developers: learn through real workflows.

Move from repository context and safe boundaries to planning, implementation, debugging, testing, and review. This is a hands-on Claude Code course for developers who want a workflow they can explain, verify, and use in production. The first module is free.

Updated September 7, 2026. Independent learning material, not an Anthropic course.

Start the free module →Test your Claude Code skills

Try free Claude Code practice exercises

Before installing anything, test two workflow decisions below. Choose once, read the explanation, and name the constraint you missed. No account, API key, or Claude subscription is needed for these browser-based questions; they do not run Claude Code or change a repository.

Practice 1 of 2

Where should project-wide Claude Code rules be placed so they apply to all team members and are version-controlled?

Answer: .claude/CLAUDE.md in the project root. Project-level CLAUDE.md lives at `.claude/CLAUDE.md` in the repo root and is committed to version control, so every team member gets the same rules. User-level CLAUDE.md at `~/.claude/CLAUDE.md` applies only to you and is never version-controlled — it's for personal preferences, not team standards.

Practice 2 of 2

You are integrating Claude Code into a GitHub Actions CI pipeline for automated code review. Which flag makes Claude Code suitable for non-interactive pipeline execution?

Answer: -p (print mode). The `-p` flag (print mode) makes Claude Code non-interactive: it executes the task, prints the result to stdout, and exits without waiting for user input. This is the correct flag for CI/CD pipelines, cron jobs, and any automated context where there is no terminal session. Combined with `allowedTools` scoped to read-only operations, it enables safe automated analysis in pipelines.

Turn the answer into a task brief

For your next small bug fix, write four lines: the observed failure, the files you expect to inspect, the action that requires approval, and the test that would demonstrate success. If you cannot identify the last two, start with the baseline lesson rather than increasing autonomy.

The preview is free. The first of four roadmap modules is also free; later modules require a paid plan. You can read the workflow explanation and compare access options without leaving ClaudeQuest.

What this course covers

A Claude Code course built around decisions, not command memorization.

Each stage produces an artifact you could use in real engineering work: a bounded task brief, a control model, a tested change, and an independent delivery review.

Free module

Bound the coding task

Give Claude Code enough repository truth and a safe definition of done.

Read repository guidance and nearby tests
Separate inspection from mutation
Define allowed files, non-goals, and approval boundaries

Open the free lesson →

Full roadmap

Control the workflow

Use scoped instructions, plans, permissions, and hooks to make work predictable.

Place instructions at the right scope
Choose when a plan is useful
Enforce critical rules with permissions, hooks, or tests

Preview this stage →

Full roadmap

Deliver with evidence

Implement, test, debug, and review a coherent change without hiding uncertainty.

Keep the change surface minimal and complete
Debug from one testable hypothesis
Review the diff as a product artifact

Preview this stage →

Full roadmap

Prove independent fluency

Run a complete task and defend the safety, evidence, and trade-offs of the workflow.

Choose an appropriate workflow without a template
Show test and review evidence
Explain remaining risk and the human decision boundary

Preview this stage →

Already use Claude Code?

Skip broad introductory material and test the decisions that often fail in production: instruction scope, permissions, evidence, recovery, and review.

Take Claude Code practice questions →Use the printable workflow checklist →

Preparing for CCA-F?

Connect Claude Code workflow skills to the wider architecture study route, then measure them in mixed scenarios.

Open the CCA-F study guide →

Start with one real workflow.

The free first module helps you bound a coding task, identify repository truth, and define evidence before making a change.

Start learning Claude Code →