In-app hints instead of a tour
Help at the moment someone is stuck, not seven modals on first login.
The prompt
You are a product designer. Replace the product tour with contextual hints. Product: {what it is} Current onboarding: {tour, video, nothing} Where people get stuck: {if known} The key action: {what they must do} Deliver: 1. Three or four moments that need a hint. A moment is not a screen but a state: empty, first time, after an error, before something irreversible. 2. For each: what to show, in one sentence, and where. A hint lives beside its element, not in the middle of the screen. 3. The show condition and the condition for never showing again. A hint that returns on the tenth visit is an irritant. 4. What the interface should solve instead of a hint. If a field needs explaining, renaming the field is usually cheaper. 5. What to delete from the tour entirely. First-login tours are watched by 20% and remembered by nobody: the person does not yet know why they would care. 6. How not to obstruct experienced users: one way to dismiss everything. 7. What to measure: share reaching the key action, before and after. Rule: a hint appears once the person is already trying to do something. Before the attempt there is nothing to explain — they do not need it yet.
Anything in curly braces is yours to replace.
Example output
Moment: an empty favourites list. Hint by the heart button: "Tap to keep a prompt here." Gone for good: after the first save. Solved by interface, not a hint: rename the "Slug" field to "Page address" and the hint becomes unnecessary. Cut from the tour: 5 of 7 steps. Keep one — where the sections are. Measure: share who copy their first prompt within the session.
Related prompts
Your idea broken down into risks plus a one-week test plan — before you spend months.
You are a product strategist who has seen plenty of projects die. Assess my SaaS idea honestly, without cheering me on. Idea: {what the service does} For whom: {who, as narrowly as possible} What the person does today without us: {how the job gets done now} How I plan to charge: {model and price} Time and money I can spend before first revenue: {resources} Break it down: 1. The problem: does it hurt regularly, or is it a one-off inconvenience? Answer plainly. 2. Who pays: the user themselves or their manager — and why that changes the product. 3. The three main risks: why this could fail. For each — the cheapest way to test it. 4. What already exists on the market, including a spreadsheet, a notebook and "do nothing" — count those as competitors too. 5. The most dangerous assumption: the one that makes everything else pointless if it's wrong. 6. A one-week test plan: what to do on which day to get a signal without writing code. 7. The kill criterion: what result means the idea should be dropped. If the idea is weak, say so in the first paragraph.
Show sample resultHide sample
Most dangerous assumption: that the bookkeeper is allowed to change tools. The finance director decides, not them — so you sell "fewer reporting errors", not "more convenient". Kill criterion: if fewer than 3 out of 20 conversations end in "let me try it", drop the idea.
The smallest set of features you can already sell, plus what's deferred and why.
Help me draw the boundary of an MVP that can actually be shipped and sold. Product: {what the service does} The main scenario: {what the user does from login to result} Who the user is: {description} Time available for development: {timeframe} Who is building it: {one developer / a team / no-code} Do this: 1. One user path from sign-up to first value — step by step, no branches. 2. The features without which that path doesn't work. Each with a reason why it can't be dropped. 3. Features that feel mandatory but aren't needed in an MVP — and what replaces them for now (manual work, an email, a spreadsheet). 4. What to cut entirely, and why it won't stop you selling. 5. The boundaries: what the product does NOT do. Wordings for the site so nobody expects otherwise. 6. An estimate in weeks, broken down, with a note on where the estimate is least reliable. 7. What can be done by hand for the first few months instead of being automated. Rule: if a feature can be replaced by a human at launch, it does not belong in the MVP.
Show sample resultHide sample
Do it by hand: PDF export is done by support on request for the first months. Three requests a week is one hour; automating it would have cost two weeks. Boundary for the site: "We don't replace your accountant — we prepare the data for them."
A feature turned into tasks with testable criteria — including errors and empty states.
This prompt is part of the PRO collection
Unlock accessTables, relations and indexes derived from your scenarios — plus where the schema will strain.
This prompt is part of the PRO collection
Unlock access