Write a How-To Guide AI Engines Will Cite

Act as a tutorial writer for content AI answer engines cite. Write a complete how-to guide structured the way Google AI Overviews, ChatGPT Search, and Perplexity reward — answer-first intro, atomic numbered steps with image cues, prerequisites, time estimate, and a paste-ready HowTo JSON-LD block.

Topic brief:
- What the reader will learn to do (verb-led): [e.g. "set up a 13-week cash flow forecast"]
- Verbatim search query: [e.g. "how to set up cash flow forecast for small business"]
- Reader skill level: [Beginner / Intermediate / Expert] · reader context: [what they have / what they're using]
- Total time: [TIME or BLANK] · cost USD: [AMOUNT, "0" if free]
- Tools required: [LIST] · supplies/assets required: [LIST]
- Brand voice: [warm-expert / no-nonsense / playful / premium / technical / friendly-everyday]
- Author name + URL: [NAME], [URL]
- Proof point for the intro: [PROOF]

Required structure:
1. H1 — verb + entity from the query, ≤12 words
2. Answer-first intro (≤80 words) — first sentence answers the query in 20-40 words and includes the proof point; ends by naming time and skill level
3. Quick reference box — time / skill / cost / tools (≤6 bullets)
4. Prerequisites — atomic checklist
5. 5-10 numbered atomic steps — imperative H2 starting with a verb; 1-3 sentence text; self-contained (no "this"/"it"/"we" without antecedent); one italic image cue
6. Verify it worked — 2-4 sentences
7. What can go wrong — 3-5 troubleshooting bullets
8. What to do next — 1-3 bullets

Output:
1. The guide in markdown, 800-1500 words; image cues only, no invented URLs
2. Complete <script type="application/ld+json"> HowTo block — name, description (the intro), totalTime ISO, estimatedCost, supply, tool, step (name + text), datePublished today, author. JSON-valid
3. Image brief — per cue: kebab-case filename, alt text (≤120 chars), what the image shows
4. Pre-publish checklist — ✓/✗ on each structural rule; flag any fact you had to assume

Success means the checklist is all ✓ before you deliver, and the step names in the JSON-LD match the H2s exactly.

Match the tone I specified above exactly; where I gave none, write plainly and warmly, the way a good operator talks to a customer — no corporate filler, no hedging phrases.

Apply every rule, limit, and format above to every item in the deliverable, not just the first one. Deliver the complete result in one response — every section filled in, nothing deferred to a follow-up.

If a required input is missing, ask for it once before starting; otherwise proceed and label any assumption you made.

Notes: R40 refresh; tuned to vendor prompting guidance