Sample Data
Never show a new user an empty product.
What it adds
Realistic demo data so a new account has something to look at and play with.
What your agent is told to do
4
What your agent is told to do
4-
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.
-
4
Never let sample data mix into exports, analytics, or billing counts.
Edge cases it handles
4
Edge cases it handles
4- Deleting sample data must not touch anything the user created.
- Sample records must be excluded from usage limits and metrics.
- A user who creates their own record first should probably not get sample data at all.
- Sample data must respect the same permissions and validation as real data.
Definition of done
6
Definition of done
6- Sample records are realistic and clearly labelled.
- One click removes all of it, and only it.
- It is excluded from exports, analytics, and usage counts.
- It obeys the same validation rules as real data.
- 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
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
Welcome Screen
Welcome Screen
Make the first ten seconds count.
What it does
A short welcome moment that orients a new user and hands them one clear next action.
How it works
- 1 Show it once, on first sign-in, and never again.
- 2 Say what the product does and give exactly one primary action. Do not list features.
- 3 Collect at most what you genuinely need to personalize the experience — every field costs you signups.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/welcome-screen
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.