PhraseryPhrasery homeGet Phrasery
Documentation21 categories

Write a getting-started guide that ends in a win

New users install the thing and then don't know what to do next.

Longtutorialonboardingwriting
Write a getting-started guide for the tool below.

Constraints:
- Define the end state first: the one concrete thing the reader will have working at the end. Pick something small and genuinely useful, not "hello world".
- State the starting assumptions explicitly: what is installed, what account exists, what the reader already knows.
- Every step is a command or an action, followed by what the reader should see. If they will see something confusing but harmless, say so.
- No step may require a decision. Choose defaults for the reader and mention alternatives afterwards.
- Target fifteen minutes. If it cannot fit, cut scope rather than rushing.
- End with a short "what just happened" paragraph and exactly three next steps.

Add a troubleshooting note for the two steps most likely to fail.

Tool:
Reader's starting point:

Making it yours

  • Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
  • Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
  • If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.

Getting someone started. READMEs, setup guides, onboarding and glossaries for the person meeting this for the first time.

Related prompts

Keep this one

Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.

Add to your browser โ€” free