Skip to content
CertLabs

CCAR-F

Claude Code: project instructions and controlled workflows

Key takeaways

  • Use project instructions for conventions and workflow context.
  • Use permission controls to govern actions.
  • Validate a change with a concrete diff and relevant checks.

Separate instructions from enforcement

Claude Code’s memory documentation describes project instruction files and automatic memory as context. They do not replace enforced configuration. Permission rules govern what actions Claude Code can perform. A sentence asking the model to avoid an operation is different from a control that prevents it.

Exercise: make a small repository change

Choose a disposable repository with a simple test suite. Write a concise project instruction file describing the build command, coding conventions, and the expected validation for changes. Ask for one small bug fix. Inspect the proposed edits and run the relevant checks.

Next, change a convention and repeat the task in a fresh session. Confirm which instructions were loaded and whether the resulting diff follows them. Avoid filling the file with facts that the code already makes obvious; focus on decisions a contributor otherwise has to ask about.

For an account-free local task, try the hands-on repository review exercise: repair a Python helper and changed caller, run the tests, then compare a separate worked solution. This synthetic exercise does not execute Claude or verify instruction loading.

Exercise: an operation requiring approval

Define an action in the disposable environment that should require explicit authorization, such as publishing an artifact. Configure the permission boundary and verify its behavior with harmless test inputs. Keep this separate from ordinary local edits.

Compare the model’s explanation with the actual permission decision. If a command is denied, investigate the rule rather than repeatedly changing wording until it happens to run. The study objective is to understand which control is responsible.

Put the concepts into practiceReview course access

Build a review habit

After each exercise, summarize the problem, the resulting behavior, the changed files, and the checks performed. Include unresolved limitations. A passing test suite covers the scenarios it contains; it does not demonstrate every possible behavior. Try one new edge case that follows from the change, then record whether it confirms or contradicts your design.

Sources and review

Source links checked 2026-10-11. These exercises are independent CertLabs preparation, not official exam questions or a prediction of passing.

Continue exploring