Clew

How to create a product tour in an app built with Cursor without a developer

A guided walkthrough in an app built with Cursor in about twenty minutes: install one line, click through your own interface in the visual editor, and publish a tour that starts where new users need it.

Time
● 20 minutes
Price
Free plan
Who does it
You and Cursor Agent

Example: a product tour in an app built with Cursor

A B2B CRM maintained in Cursor. Sales reps who open /deals get a 5-step tour: pipeline stages, dragging a deal, the next-action field, filters, and the forecast total.

Free on the Clew Free plan — no card, no time limit: one site and up to 3 published tours or tooltips. Audience rules and A/B tests come with Pro.

How to build the product tour in an app built with Cursor, step by step

  1. Step 01

    Copy your Clew snippet

    Create a free account (or sign in), add your site and open Admin → Overview. Click the line in the “No signal from the widget yet.” card to copy it — it carries your real site key instead of the placeholder.

    <!-- Clew: replace PASTE_YOUR_SITE_KEY with the site key from Admin > Overview -->
    <script src="https://tryclew.io/widget/PASTE_YOUR_SITE_KEY.js" async></script>
    Clew admin Overview with the embed line and a masked site key (product tour in an app built with Cursor)
    Step 1 · schematic illustration
  2. Step 02

    Open the repository in Cursor, Agent mode

    Open the project folder in Cursor and the chat in Agent mode, so it can edit files itself.

    Code editor with the AI agent chat panel open (product tour in an app built with Cursor)
    Step 2 · schematic illustration
  3. Step 03

    Send the prompt with your key

    Replace PASTE_YOUR_SITE_KEY with your key and send it. Cursor reads the repository and picks the right root file from the list in the prompt.

    Add the Clew onboarding widget to this app.
    
    Insert this exact tag once so it loads on every page, including after client-side route changes:
    <script src="https://tryclew.io/widget/PASTE_YOUR_SITE_KEY.js" async></script>
    
    Find the root HTML file or root layout of this project (index.html for Vite, app/layout.tsx with next/script for Next.js App Router, nuxt.config.ts app.head.script for Nuxt, src/app.html for SvelteKit) and add the tag there.
    
    Also add stable data-tour attributes to the elements a product tour will point at: the main navigation, the primary create/add button, the main filter or search, and the page heading — for example data-tour="create-button". Do not change their styles, text or behaviour.
    
    Rules:
    - Use the script URL exactly as given. Do not download it, bundle it or install an npm package.
    - If the project sets a Content-Security-Policy, allow https://tryclew.io in script-src and connect-src.
    - Change nothing else and show me the diff.
    AI chat with the Clew prompt in the message box (product tour in an app built with Cursor)
    Step 3 · schematic illustration
  4. Step 04

    Accept the diff, commit and deploy

    Review the diff — the tag in one root file plus the prompt’s small additions — then accept, commit and push. Your hosting deploys as usual.

    Code diff with one script line added to the root file (product tour in an app built with Cursor)
    Step 4 · schematic illustration
  5. Step 05

    Build the tour on top of your page

    In Clew open Flows → + New flow, keep Format at Step-by-step tooltips and press Edit on your site. On your page press Pick element and click the element for step 1, then write a title and one or two sentences. Repeat for 3–5 steps; the preview updates as you type.

    A product tour tooltip pointing at a button in a web app, with step dots and a Next button (product tour in an app built with Cursor)
    Step 5 · schematic illustration
  6. Step 06

    Choose where, when and for whom it shows

    In the same editor, set Where to show (page URL), When to show, Audience targeting and Frequency. These are the settings of the example above:

    SettingValue
    FormatStep-by-step tooltips
    Where to show (page URL)Section by prefix /deals
    When to showRight on page load
    Audience targetingNo rules — everyone who opens the page
    FrequencyOnce per visitor
    Clew tour editor with the format, page URL rule, trigger and audience rule fields (product tour in an app built with Cursor)
    Step 6 · schematic illustration
  7. Step 07

    Publish and check it on the live site

    Set Status to Published and save. Open the page in a private window — Clew remembers who has already seen a “once” item, so your usual browser may skip it. Views, completions and drop-offs appear in the tour stats.

    Clew admin Overview with the green “Widget is live” card (product tour in an app built with Cursor)
    Step 7 · schematic illustration

Pitfalls: product tour in an app built with Cursor

Review before accepting

Agents sometimes “improve” nearby code. Reject changes outside the files the prompt mentions; the product tour needs nothing else.

Local dev isn’t production

The widget works on localhost too, which is great for testing, but visitors’ stats and the “Widget is live” signal come from the deployed app.

Generated class names change on every rebuild

AI-built apps often use utility classes or hashed CSS modules. A selector like .bg-blue-600.px-4 breaks after the next prompt. That’s why the prompt above asks for data-tour attributes: pick those elements and the tour survives regenerations.

Questions and answers

Can I keep the tour in the repository?

The tour content lives in Clew so non-developers can edit it. The repository only holds the line and the data-tour attributes.

Which Cursor model should I use?

Any model in Agent mode handles this; the task is small and the prompt names the files.

Is the product tour free?

Yes — tours are on the Free plan with up to 3 published. You only need Pro for audience rules, A/B tests and more tours.

Can’t I just ask the AI to build the tour?

You can, but then every text change is a new prompt, a new diff and a new deploy, and you get no stats. With Clew the AI adds one line and a few attributes once; the tour itself is edited in minutes by anyone on the team.

One line on your site — then tours, tooltips and checklists without releases.

Get your site key — freeHow Clew worksFree plan forever, no credit card

Product tours, popups and onboarding in the age of AI

7 patterns with step counts, copy rules and what to measure, what AI changes, and a checklist before you publish. PDF, 2 pages. What is inside →