Write a Help Center How-To Article That Actually Helps

This prompt writes a help center how-to article structured the way users actually consume support content: a one-line summary, prerequisites, numbered steps with screenshot cues, a success check, and troubleshooting for the two most common failure points. Use it when documenting a specific task in your product for a defined skill level. The 'no corporate fluff, direct second-person voice' rule is deliberate — support readers are mid-problem and want the next action, not a paragraph of preamble.

What you can expect back

How to set up two-factor authentication

Add a second login step so a stolen password alone can't get into your Hubble account.

Before you start
- You're logged in to Hubble on a desktop browser.
- You have an authenticator app (Google Authenticator, Authy) installed on your phone.

Steps
1. Click your avatar (top right) and choose Settings. [Screenshot: avatar menu open, Settings highlighted.]
2. Open the Security tab and click Enable two-factor. [Screenshot: Security tab with the Enable button.]
3. Scan the QR code with your authenticator app. [Screenshot: QR code panel.]
4. Enter the 6-digit code from the app and click Confirm. [Screenshot: code entry field.]

What success looks like
You see a green 'Two-factor enabled' badge and a list of backup codes — save these somewhere safe.

Troubleshooting
- Code rejected? Your phone clock may be off; enable automatic time sync and retry.
- Lost your phone? Use a backup code at login, then re-enroll a new device.

Illustrative example — your results will vary by tool and inputs.

Get sharper results

• 01Phrase the task title exactly how users would type it into search, since the article only helps if people find it.
• 02Give the model your real UI labels (button names, menu paths) so the steps match what users see instead of plausible-sounding guesses.
• 03Set the user level honestly — a beginner article that assumes admin knowledge is the fastest way to generate more support tickets.
• 04Tell it the two failure modes your support team actually sees, so troubleshooting solves real problems rather than hypothetical ones.
• 05Treat the bracketed screenshot descriptions as a shot list for whoever captures the images, then replace them with real screenshots before publishing.

Adapt it for your case