How to read a detail guide
Claude Code: Read detail guides in order: availability, concrete examples, persistence, and official evidence.
Key takeaways
- Syntax notation explains the interface; concrete examples show actual input.
- Do not infer cross-session persistence when a setting does not document its scope.
From prerequisites to checking the result
- Purpose explains the task and exact syntax.
- Availability gives the input surface, status, aliases, and documented minimum.
- Examples use concrete values. Replace paths and task names; separate lines are separate invocations.
- Effects and persistence identifies display, session, file, settings, or cloud effects.
- Cautions explains command-specific exceptions.
- Official sources links the evidence and earlier change records.
When a command is missing
Check the installed version, account, platform, model, and feature settings. Use /help or the / menu in Claude Code. Also check whether the instruction belongs in the operating-system shell or inside the running session.
Korean and English editions
Both editions share command syntax, status, sources, and detail-page order. Extended operational explanations may differ in length. Historical records preserve the content of the edition at the time.