Instruction files
Claude Code uses CLAUDE.md for project context, with other instruction sources documented separately, while Cursor project rules use .mdc files in .cursor/rules and metadata that controls when they apply. Both products document AGENTS.md support, but that does not establish identical discovery, scope or precedence. Check the installed version. These facts were checked November 14, 2026.
For a fictional booking API, keep a reusable rule about preserving timezone offsets near the code it governs. Keep a temporary bug report in the task. Copying all instructions into every prompt makes it harder to see which rule applies to the current change.
Task and review
Give either product a bounded task with an acceptance condition. A repair to duplicate bookings needs a repeated-request case and a valid new booking. Ask for the relevant test results and inspect the diff yourself. A product’s ability to edit files or invoke a tool is separate from permission to change production data.
The right review question is whether the changed behavior meets the requirement. A patch can compile and still reject valid bookings. A model can describe a test without running it. Keep the evidence visible when you decide whether to accept the work.
Practice and product choice
The Claude Code tutorial and Cursor rules tutorial teach these conventions with fictional scenarios. The course workspace uses prepared assistant replies. It does not install either product or compare their model quality, speed, plans or prices.
Choose a product by testing it in your own approved environment, with the same bounded task and checks. Use its documentation for current permissions, integrations and account availability. Continue with the coding-agent course for instruction files, skills and code review practice.