Write a How-To Tutorial Blog Post with Checkable Steps and Troubleshooting

You get a complete tutorial post with prerequisites, numbered one-action steps that each have a checkable expected result, a troubleshooting table and next steps.

Prompt

Prompt
Act as a technical writer who writes step-by-step tutorials for blogs.

Your job: write a how-to tutorial blog post. Before writing, ask me these questions in one numbered message and wait for my answers:
1. What should the reader be able to do by the end?
2. What is the reader's skill level (beginner, some experience, advanced)?
3. Which tools, software versions and operating system will they use?
4. What problems do readers often hit, if you know any?

Rules:
- Each step has exactly one action, starting with a verb, followed by an "Expected result:" line the reader can check.
- Match vocabulary to the skill level; define any term a beginner may not know the first time it appears.
- List every prerequisite (accounts, installs, permissions, time needed) before step 1.
- Troubleshooting covers at least 3 problems, each tied to the step where it happens, with cause and fix.
- Do not guess menu names, commands or version details you are unsure of; mark them "(verify)".

Output format:
1. Title (under 70 characters)
2. Intro: 2-3 sentences on the result and time needed
3. Prerequisites (bullets)
4. Steps (numbered: action, then Expected result)
5. Troubleshooting (table: Problem | Step | Likely cause | Fix)
6. Next steps (2-3 bullets)

End with one line listing assumptions you made or details I should confirm.

Example output

At a glancePublishing a site with GitHub Pages in 7 stepsAbout 20 minutes with only a web browser
  1. Create a new repositoryClick + in the top-right and choose New repository
  2. Name it yourusername.github.ioA green check mark appears next to the name
  3. Make it Public and createAn empty repository page opens
  4. Create index.htmlAn empty text editor opens
  5. Paste a heading and commitThe repository lists one file, index.html
  6. Check Settings, then PagesConfirm the main branch; your site address shows
  7. Visit your siteWait 2 minutesYour heading appears on a white page

Example for: a beginner publishing a one-page personal website with GitHub Pages, using a web browser on Windows, no coding tools installed.

Publish Your First Website Free with GitHub Pages

By the end of this guide you will have a live one-page website at a free web address. It takes about 20 minutes and you only need a web browser.

Prerequisites

  • A free GitHub account (a website that stores project files online)
  • A web browser such as Chrome, Edge or Firefox
  • About 20 minutes
  • Your GitHub username written down; it becomes part of your site address

Steps

  1. Click the + icon in the top-right corner of GitHub and choose "New repository."
    Expected result: a page titled "Create a new repository" opens.
  2. Type yourusername.github.io in the Repository name box, using your real username.
    Expected result: a green check mark appears next to the name.
  3. Select "Public," then click "Create repository."
    Expected result: you see an empty repository page with a "creating a new file" link.
  4. Click "creating a new file" and name the file index.html.
    Expected result: an empty text editor opens under the file name.
  5. Paste <h1>Hello, I'm Dana</h1> into the editor and click "Commit changes" (save).
    Expected result: the repository now lists one file, index.html.
  6. Open Settings, then Pages (verify: in the left sidebar), and confirm the source is the "main" branch.
    Expected result: a message shows your site address.
  7. Wait 2 minutes, then visit https://yourusername.github.io.
    Expected result: your heading appears on a white page.

Troubleshooting

ProblemStepLikely causeFix
Red warning next to the name2Username misspelled or wrong letter caseCopy the username exactly from your profile, in lowercase
Page shows "404 – There isn't a GitHub Pages site here"7Site still buildingWait 5 more minutes and refresh
Site shows raw code text instead of a heading5File saved as index.txtRename the file to index.html
No site address in Pages settings6Source branch not setChoose "main" and "/ (root)," then click Save

Next steps

  • Add a short bio paragraph under your heading.
  • Create an about.html page and link to it.
  • Connect a custom domain once you are comfortable.

Assumptions: GitHub's current menu labels and default "main" branch; confirm the Pages location in Settings, as GitHub occasionally moves it.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Asking skill level and exact tools first stops the model from writing a generic guide that skips steps or over-explains.
  • One action plus an expected result per step lets readers confirm they are on track before moving on.
  • Marking unsure menu names as (verify) stops confident-sounding wrong instructions from reaching your readers.

Use when you need a tutorial post for a blog, help center or newsletter. Know the end goal, your reader's level and the exact tools. Works in ChatGPT, Claude or Gemini; test the steps yourself before publishing.

Common edits

  • Add a screenshot placeholder note after each step so you know where to insert images.
  • Ask for a shorter version as a 5-step checklist for social media or an email newsletter.

Prompt details

By
Prompts-GPT editors
Published
How prompts are written and checked

Did this prompt work?

Keep exploring

More in Writing