Make your first change

Make the reservation time limit clear before a visitor books. Complete Explore a working app first, then keep that Ticketing copy and its local Devboard open.

Before editing, inspect the current test results with your agent. Establish any existing failures separately so they are not mistaken for a result of your change.

Ticketing tutorialContinue from Explore a working app

1. Agree on one visible result

   Ask your agent

   Show “Your places are held for up to 15 minutes while you complete your booking.” just before Reserve tickets, replacing the old guidance. Keep it readable on a phone and keep the booking rules unchanged.

   The app already has this reservation limit. Keep one clear explanation of it. If your copy already contains the sentence, improve its placement instead of adding it twice. Let the agent implement the change and show the result in Devboard.

2. Inspect the change

   Wait for the agent to confirm the new build is running. A failed build can leave the previous working version in the preview.

   Return to Night Lights, open its performance and select places. Read the sentence before reserving. Narrow the browser window: the text should remain readable and the reservation action should remain reachable. Reserve a group and check that the existing temporary hold still works.

   If the wording is hard to find, describe the screen and what you expected. For example: “The sentence wraps well, but I only see it after scrolling past the Reserve button. Put it immediately before that action.”

   You should see

   The hold explanation appears immediately before Reserve tickets, stays readable on a phone, and the temporary reservation still works.

3. Check the evidence with your agent

   Ask the agent to show the check for the new text and the relevant existing reservation scenarios. The managed environment selects and runs affected tests as files change. The agent should inspect those results and identify any additional verification needed, rather than starting a second competing build loop.

   Some checks may belong to a frontend test runner or a browser inspection instead of the Devboard scenario list. Ask where each result can be found. Confirm that the check covers the actual displayed behavior, and that reservation expiry has not been changed just to match the copy.

4. Save a reviewed checkpoint

   Once the result is right, ask the agent to summarize the change, record the completed work in Progress and save a Git commit in your tutorial copy. A commit records the code change; it does not publish the app or save the local demo’s reservations.

You have taken one change through a complete loop: describe → implement → inspect → verify → save. For a larger product feature, follow Check and improve a feature. To start a different product, use Start an app from your idea.