How to add an onboarding checklist in an app built with Cursor without a developer

Example: an onboarding checklist in an app built with Cursor

How to add the onboarding checklist 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>

   Copy

   

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.

   

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.
   
   After the signed-in user is loaded, and whenever these values change, call Clew.identify() with a few non-personal properties as strings — for example { plan: "trial", role: "owner", onboarded: "false" }. If the widget may not have loaded yet, first define the queue stub: window.TutorKit = window.TutorKit || { q: [], identify: function (p) { this.q.push(["identify", p]); } }; and call window.TutorKit.identify(...). Never pass names, emails or other personal data.
   
   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.

   Copy

   

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.

   

5. Step 05

   Write the checklist items in Clew

   In Clew open Flows → + New flow and choose Onboarding checklist. Fill Checklist title, then add 3–5 Checklist items: a title that is an action, one line of explanation and in Link URL the page where it is done. No selectors are needed.

   

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:

   Setting	Value
   Format	Onboarding checklist
   Where to show (page URL)	Section by prefix /deals
   When to show	Right on page load
   Audience targeting	Property team_invited does not exist
   Frequency	Once per visitor

   

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.

   

Pitfalls: onboarding checklist in an app built with Cursor