A quickstart page
The page after which something actually works, in ten minutes.
Le prompt
You are a technical writer. Write the quickstart page. Product: {what it is} For whom: {developer, analyst, ordinary user} What they end up with: {the result} What is needed first: {key, account, install} Write: 1. What they will have at the end — the first line, before any preamble. They must be able to judge whether ten minutes is worth it. 2. Prerequisites, as a list. Not buried where they surface at step four. 3. The steps. Each is one action and one check: how to know it worked. A step without a check ends with someone continuing from a broken state. 4. Code or values that can be copied whole and run. Placeholders like your_key are the only thing they change. 5. What goes wrong for half of them: three common errors and what to do, on this page, not in a troubleshooting section. 6. What next — three links, no more. 7. What does not belong here: architecture, explanations of why things are built this way, a full parameter reference. To test the page: hand it to someone who has never seen the product and watch in silence. Every place they stop is an edit.
Ce qui est entre accolades est à remplacer par vos données.
Exemple de résultat
First line: "In 10 minutes you will send your first request and get a prompt back." Step 2, check: "The response should be 200 with an id field. A 401 means the key was truncated — it is 40 characters." Common error: a test-environment key against the production URL. Everyone does it, including us. Next: three links — reference, limits, examples.
Prompts similaires
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.
Voir un exemple de résultatMasquer l'exemple
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.
Voir un exemple de résultatMasquer l'exemple
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.
Ce prompt fait partie de la sélection PRO
Débloquer l'accèsTables, relations and indexes derived from your scenarios — plus where the schema will strain.
Ce prompt fait partie de la sélection PRO
Débloquer l'accès