Setup Checklist
A persistent checklist that pulls users toward activation.
What it adds
A dismissible checklist of the steps that make a new account genuinely set up.
What your agent is told to do
4
What your agent is told to do
4-
1
Pick the 3–5 steps that correlate with a user actually sticking around. Not every setting — the ones that matter.
-
2
Derive each step's completion from real application state, not from a checkbox the user ticks.
-
3
Show progress, and celebrate completion — then get out of the way permanently.
-
4
Let users dismiss it early without losing the ability to find it again.
Edge cases it handles
4
Edge cases it handles
4- Steps completed before the checklist existed must show as done for existing users.
- A step that becomes irrelevant (a plan change, a disabled integration) must drop off the list.
- The checklist must disappear for good once complete — do not resurrect it.
- Do not count a step complete if the user did it and then undid it.
Definition of done
7
Definition of done
7- Completion is derived from real state, never a manual checkbox.
- Existing users see accurate progress.
- The checklist is dismissible and restorable.
- It disappears permanently once finished.
- Progress is per-user and persists across devices.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
First-Run Onboarding
First-Run Onboarding
Guide new users to the action that makes your app click.
What it does
A first-run experience that gets a brand-new user to their first meaningful outcome.
How it works
- 1 Identify the single action that makes this product valuable — the moment a user 'gets it'. Everything in onboarding serves that one moment.
- 2 Build a short checklist of the steps leading there. Three to five items, no more.
- 3 Track completion per user, server-side, so it survives a device change.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/first-run-onboarding
Sample Data
Sample Data
Never show a new user an empty product.
What it does
Realistic demo data so a new account has something to look at and play with.
How it works
- 1 Generate sample records that look like real usage, not 'Test 1, Test 2'. The point is to show the product working.
- 2 Mark sample records clearly so nobody mistakes them for their own data.
- 3 Give the user a one-click way to remove all of it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/sample-data
Guided Product Tour
Guided Product Tour
Walk new users through the interface without a video.
What it does
A short, skippable tour that highlights the parts of the UI that matter.
How it works
- 1 Keep it to 3–5 stops. A long tour gets skipped, and a skipped tour teaches nothing.
- 2 Anchor each stop to a real element, and highlight it by dimming everything else.
- 3 Let the user leave at any point, and remember that they did.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/guided-product-tour
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.