All posts

How to add a product tour to your app with Cursor, Claude Code or Lovable

Build the tour by clicking through your app. Then hand your AI coder one file and one prompt. It is the smallest change it will make to your project all week.

4 min read
Isometric illustration of a chat panel with a short prompt bubble next to a small script file with a blue corner

If you built your app by prompting, you probably expect a product tour to be another prompt: “add onboarding”. That gets you a tour library in your dependencies and steps hard-coded in your components, and every copy change becomes a new prompt.

There is a shorter route. You build the tour by clicking through your running app, and your AI coder only does the one thing it is good at here: putting a file in the right place and adding a script tag. This guide walks through both halves.

What you need

  • Your app running somewhere you can open in Chrome: the live site, a preview deploy, or localhost.
  • The Stepsome extension. No account, no sign-up.
  • Your AI coder of choice, with access to the project: Cursor, Claude Code, Lovable or similar.

Build the tour on the address your users will use. Stepsome keeps tours per website, so a tour built on localhost:3000 belongs to that address. If you work on a staging address as well, add it under Also on in Settings → Websites so it shares the tours of your main site.

Part 1: build the tour by clicking

  1. Open your app and press Alt Shift T, or click the Stepsome icon. The editor appears as a bar at the bottom of the page.
  2. Choose Add steps by clicking and click through your app the way a new user should. Each click becomes a numbered step. Buttons become a step to click, fields a “Fill in” step.
  3. Press Alt P to pause if you need to use the app without adding steps, and Undo to take back a wrong click.
  4. Click Done. Then click each step number and type over the text in the tooltip.
  5. Press play to watch it the way a visitor will.

Keep it short: three to five steps to the first useful result. How to write product tour copy helps with the text.

Part 2: publish and download the site file

Click Publish in the bar and set the tour to Published. Then open the dashboard’s Install page and click Download. You get one file called stepsome-<your-site>.js that holds everything you published for this website.

The file is self-contained: no dependencies, nothing loaded from another server, and it only draws something when a tour or widget should show.

Part 3: let your AI coder install it

On the Install page, click Copy prompt for my AI coder. It copies a prompt like this, with your own file name filled in:

Add Stepsome (product tours and widgets) to this project.

1. I downloaded stepsome-app-example-com.js. Put it in the public/static
   folder so it is served at /stepsome-app-example-com.js.
2. Add <script src="/stepsome-app-example-com.js" defer></script> just
   before </body> in the main HTML layout so it loads on every page.
3. Do not change anything else. The file is self-contained and has no
   dependencies.

Get the file into the project first, then paste the prompt:

  • Cursor or Claude Code: drop the downloaded file into the project folder, anywhere. The assistant moves it to public/ (or static/, depending on your framework) and adds the tag to your root layout.
  • Lovable and other browser builders: if the tool syncs with a GitHub repository, commit the file to its public/ folder there, then paste the prompt so the assistant adds the script tag.

Rule 3 in the prompt matters. Assistants like to be helpful, and you do not want a wrapper component or an npm package added around a single script tag.

Deploy as you normally would.

Check that it works

  1. Open https://your-app.com/stepsome-<your-site>.js in your browser. You should see JavaScript, not a “not found” page. If it is not found, the file is not in the folder your framework serves from the root.
  2. Open your app in a private window. A tour set to start on the first visit should start. A private window has no “already seen” history, so you can do this as often as you like.
  3. Nothing? View the page source and search for stepsome-. If the tag is missing, the assistant put it in a layout that not every page uses.

In the dashboard, the Install page now says Up to date.

Changing the tour later

This is where the approach pays off. To change a word, open the editor on your app, click the text and type. No prompt, no diff to review.

The one thing to remember: your website shows the file you deployed last. After a change, the Install page says Your site file is out of date. Click Update file, replace the old file in public/ with the new download (same name, so the script tag stays the same) and deploy. With an AI coder, “replace public/stepsome-app-example-com.js with the file I just added” is enough.

If your next prompt rewrites a component and a step can no longer find its element, the tour does not get stuck: the step shows as a card in the middle of the screen. To catch it before your users do, see Why product tours break after a deploy.

Optional: a “Show me around” button

Visitors who skip the tour may want it later. Two ways to offer it:

  • Switch on Replay button on the Install page and download the file again. Your app gets a small “Show me around” button.
  • Or ask your AI coder to add a menu item that calls Stepsome.start(), for example under Help.

Once the tour is live, record a demo video from the same steps: Make a launch video of your side project in 15 minutes.