Claude Code Guides

The official Claude Code documentation answers what a thing is. These guides answer why it isn’t working on your machine, in your repo, with your stack.

That is the whole editorial rule. Every guide opens on a symptom someone actually typed into a search box, walks the diagnosis in order, and ends with something you can keep.

These are not the ClaudeFlow docs

This section documents Claude Code, the tool. If you are looking for how the ClaudeFlow kit itself works — installing it, what ships in it, how the agents are wired — that lives in the product docs.

Troubleshooting & config

The first wave. High-intent, evergreen, and every one of them ends in a file you can drop into a project.

Nothing works

Claude Code is behaving badly and you don’t know which layer is at fault. Diagnose by symptom instead of guessing.

Diagnose by symptom →

Config ignored

You edited a settings file and nothing changed. Almost always precedence — another file is winning.

Find the file that wins →

settings.json

The settings file that earns its place in a real repo, grouped by what each field actually changes.

Read the walkthrough →

How these guides are built

Each one follows the same shape, because the shape is what makes them useful under pressure:

1. The symptom — stated the way you would describe it out loud.
2. What is actually happening — the mechanism, briefly.
3. The diagnosis — ordered steps, cheapest check first.
4. Common mistakes — the wrong turns that cost people an afternoon.
5. A checklist — the part you keep.

Official Claude Code documentationThe canonical reference from Anthropic. Every guide here links back to the page it builds on.