Claude Code tutorial and CLAUDE.md
Project context
Start a Claude Code task by identifying the behavior you want to change and the files involved. CLAUDE.md stores project context you want available across tasks. Keep temporary instructions, such as a particular failure report, in the current task.
For a fictional booking service, a useful instruction is: “Use the existing booking validator. Run booking tests after changes. Keep timezone offsets in request fixtures. Never read production credentials for local tests.” It points to code and states boundaries without repeating a programming textbook.
A checked change
Ask for the cause of the bug before an edit, inspect the proposed scope and check the diff afterward. If the bug concerns two bookings sharing a start time, require a test that reproduces that condition. A statement that the task is complete does not show which code ran.
The Claude Code memory documentation, checked November 14, 2026, explains CLAUDE.md and its loading behavior. It also distinguishes written guidance from enforced controls. Put a recurring procedure in a reusable skill when it needs a separate trigger.
The practice assistant uses prepared replies. For live execution and installation, use the vendor’s current quickstart. Compare Claude Code and Cursor before copying configuration between products.