First steps with Claude Code

How do you get started with Claude Code?

1250 € per session, excl. VAT

In short

Half a day to get to grips with Claude Code: this three-hour half-day session introduces Claude Code using a secure exercise folder. Participants learn to find their way around, formulate a bounded instruction, review a change and carry out simple checks. They leave with a method for getting started, with no prior knowledge of AI or programming required.

Why this training?

A seemingly simple request, such as correcting a time on a page, can lead to more files being changed than expected. Discovering Claude Code therefore involves understanding the scope entrusted to the assistant and distinguishing a plausible proposal from a verified change. The introduction prioritises small, visible steps: ask for an explanation, clarify the expected change, review and then test. This approach helps beginners retain control of their files without assuming that generated code is automatically correct or safe. Running case study: The fictitious association Rivage Papier is preparing a reading event. It has a small local page presenting the programme. Participants must understand its files, correct a time, add an arrival instruction and check the result, without collecting data or publishing anything. Transfer to the workplace: After the session, reuse the instruction sheet on a copy of a non-sensitive folder authorised by the organisation. Choose a limited change, keep the original and document the checks; request a review by someone suitably qualified before any real-world use of the code.

Objectives of this training

  • Locate the input area, responses and working folder in the environment presented.
  • Formulate an instruction specifying the file concerned, the expected change and the limits.
  • Distinguish a proposed explanation from a change that has actually been made.
  • Compare files before and after an intervention.
  • Carry out a simple check and report an observed anomaly.

Who is it for and what are the prerequisites?

Roles and tasks concerned

  • Non-developer staff wishing to explore coding assistance for basic tasks.
  • Project leads and staff in support functions wishing to understand how to set boundaries for an initial request to Claude Code.

Prior skills

  • No prior knowledge of AI or programming required.
  • Ability to open a folder and enter text; support can be provided with these actions.

What you will work on

  1. Explore the environment without making changes

    Objective: Identify where the user and the assistant work. Orientation in the available interface, the concepts of folders and files, and the difference between an instruction and a response. Details of use should be checked in the official documentation.

  2. Write a bounded request

    Objective: Turn a practical need into a verifiable instruction. Context, target file, expected result and exclusions. Generating and modifying code from instructions; the need for human review.

  3. Review and verify the change

    Objective: Check a result rather than relying on the report. Comparison with the original, guided review of the changes and local verification. An affirmative response from Claude Code does not constitute a test.

  4. Carry out a second task within defined limits

    Objective: Repeat good practices with less assistance. Managing secrets, exercising caution with proposed actions and keeping a copy. Stopping and asking for help when an action is not understood.

What you take away

  • Instruction sheet with a defined scope for Claude Code.
  • Copy of the modified exercise page and retained original version.
  • Log of observed changes and checks carried out.
  • Safety checklist for subsequent operations.

Method and assessment

  • Short explanations followed by immediate practice using the running case study.
  • Individual work followed by work in pairs, with peer review of the outputs.
  • Guided group discussion: what works, what needs correcting and what remains a human decision.
  • Preparation: Have a workstation with access to Claude Code authorised by the organisation; check that it works before the session, following the official documentation. Prepare a fictitious training folder, an original copy and safety instructions; exclude personal data, passwords and access keys.

Observable criteria: The participant identifies the exercise folder before requesting a change. ; The instruction states the expected change and prohibits changes outside the defined scope. ; The comparison identifies the changes made in the file concerned. ; The check confirms the time and the arrival instruction, or documents their non-compliance. ; The participant explains why no secrets should be passed to the assistant..

Frequently asked questions

Do you need to know how to code?

No. The files are short and provided; guidance is given when reading them, without any in-depth study of a programming language.

Can you use work files?

The exercises use fictitious or anonymised cases, only in environments authorised by the organisation.

Is installation included in the three hours?

Working access is prepared in advance so that the 180 minutes can be devoted to discovery and exercises.

Will the page be deployed to production?

No. It remains a local exercise; the tests carried out do not constitute approval for publication.

Last updated: