Guided adjustments using prompts

How can you request a targeted change in Lovable and check that it does not impair the existing journey?

  • Lovable
  • Claude Code
  • Codex

1250 € per session, excl. VAT

In short

This half-day session of 3 hours offers a guided introduction to modifying an existing application in Lovable. Participants formulate precise instructions, observe the changes and test a simple user journey. They leave with a modified practice version, a prompt log and a completed verification checklist.

Why this training?

A request such as ‘make this page clearer’ leaves many choices implicit: text, button placement and expected behaviour. Describing the screen concerned and the elements to preserve helps define the scope of the requested change more clearly. A visually improved screen can conceal a button that no longer works or an inconsistent confirmation. The workshop pairs each adjustment with an observable check and distinguishes the assistant’s response from the behaviour actually observed. Continuing case study: The fictional organisation ‘Avelune Ateliers’ uses a demonstration application to present its creative workshops. Visitors confuse two buttons and struggle to understand the registration confirmation. Using fictional data, participants clarify the labels, add an instruction and check that the journey remains usable. Transfer to work: Reuse the prompt template to describe a small interface adjustment within your organisation, without sharing sensitive data. Have the scope and test environment approved before making any changes, then compare the observed behaviour with the written criteria.

Objectives of this training

  • Identify the screen, text and action concerned by a request.
  • Write a prompt specifying the expected change, boundaries and elements to preserve.
  • Make a guided adjustment in the practice application.
  • Compare the result obtained with the criteria defined before the change.
  • Record a defect and formulate a targeted corrective request.

Who is it for and what are the prerequisites?

Roles and tasks concerned

  • Beginners wishing to explore interface adjustments without starting by learning a programming language.
  • Business activity managers who need to describe small application changes to a technical team.

Prior skills

  • No prior AI knowledge or coding knowledge required.
  • Ability to navigate a web application and describe a simple user journey.

What you will work on

  1. Observe before asking

    Objective: Define the scope of an initial adjustment without transforming the entire application. Identifying the screens and initial journey; the difference between appearance and behaviour; generating and modifying code from instructions.

  2. Write a bounded instruction

    Objective: Translate an interface ambiguity into a verifiable request. Prompt structure: context, screen, change, constraints and expected result. One change at a time to make observation easier.

  3. Observe and correct progressively

    Objective: Refine a change based on an observed discrepancy. Reading the accessible changes, human review and secrets management. General positioning of Claude Code and Codex for working on code; consult their official documentation for the relevant arrangements.

  4. Check the complete journey

    Objective: Measure whether the adjustments meet the requirements without equating demonstration with production. Manual tests: access to a workshop, button activation, visible instruction and understandable confirmation. Counting the criteria met and recording defects.

What you take away

  • Adjustment sheet: screen, change, boundaries and expected criteria.
  • Modified version of the practice application, usable for demonstrating the journey.
  • Log of initial and corrective prompts.
  • Completed test checklist with discrepancies and remaining limitations.

Method and assessment

  • Short explanations followed by immediate practice on the continuing 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 access to Lovable authorised by the organisation and check the access conditions required for the exercise in the official documentation. Prepare a practice application separate from any real environment, containing only fictional or anonymised data and no secrets.

Observable criteria: The prompt identifies a specific screen and indicates at least one element to preserve. ; The resulting labels match the approved request. ; The journey is completed before and after the change, with results recorded. ; Each observed anomaly is described through an action, an expected result and an observed result. ; No sensitive data or secrets appear in the prompts..

Frequently asked questions

Do you need to know how to programme?

No. The adjustments are guided; any technical change that is not understood must be submitted for competent human review.

Are all three tools used?

The practical work focuses on Lovable. Claude Code and Codex are positioned as complementary approaches, with no assumed integration or mandatory access.

Can we work on our real application?

The exercise uses a separate environment and fictional or anonymised data, with only the tools authorised by the organisation.

Will the application be put into production?

No. The deliverable is used to demonstrate and verify the adjustments; any real deployment requires additional checks.

Last updated: