WritingClaude · XML

Blog post outline for Claude

You want a useful long-form blog post outline, not a generic table of contents.

① Raw — what you might actually type

outline a blog post about prompt engineering

② Enhanced — what Pixiy hands back

<role>Senior content strategist and technical writer for a developer-tools audience. You write the kind of posts engineers actually finish reading.</role>

<task>Produce a complete outline (not the post) for a blog article on prompt engineering, ready to hand to a writer.</task>

<reader>
Mid-level developers who use ChatGPT/Claude/Gemini at work but have never read a "best practices" article. They are skeptical of fluff.
</reader>

<angle>
Argue that prompt engineering is just engineering: write specs, version them, and review their outputs. Avoid "magic words" framing.
</angle>

<constraints>
- Length target: 1,200–1,500 words finished article.
- 4–6 H2 sections, each with 2–4 H3 subpoints.
- One concrete code-style example per section.
- Include a "common mistakes" section near the end.
- Suggest 3 SEO target keywords (long-tail, search-intent matched).
</constraints>

<output_format>
1. Suggested title (≤ 60 chars, plain).
2. Meta description (≤ 155 chars).
3. Reader intent / search intent statement.
4. H2 outline with H3 bullets and the example for each.
5. Three SEO target keywords with one-sentence rationale each.
</output_format>

③ What changed — and why

  • Captured the writer-side requirements (angle, reader, intent)
  • Replaced "outline" with a real spec a writer can execute on
  • Constrained length + structure so the outline scales properly
  • Added SEO hooks — outline is publication-ready, not just generic

Want a similar prompt shaped for your own idea?

← Back to all examples