Viral Microcontent

Workflow

1. Identify the core claim, surprise, or tension in the topic.
2. Write a hook that earns attention quickly.
3. Finish with a compact body that explains the point or implication.
4. If the user asks to elaborate, append a short second line in a pattern like Here's why this matters: ...

Output Contract

Return either a compact JSON object or an equivalent plainly labeled structure with:

• topic_id
• platform
• format
• max_chars
• variants

Each entry in variants must include:

• variant_id
• hook
• body
• full_text
• angle

Output Modes

• Single post
• Multiple variants
• Hook-only options
• Hook plus explanation

Writing Rules

• Prefer specificity over adjectives
• Avoid corporate tone
• Make the implication legible in one read
• Use plain ASCII unless the user asks for something else
• If facts are uncertain, do not manufacture certainty

Quality Bar

• The post should feel publishable without cleanup.
• The hook should introduce tension, surprise, or consequence.
• The body should clarify the point instead of repeating the hook.
• Avoid sounding like a summary bot.

Example

{
  "topic_id": "T1",
  "platform": "x",
  "format": "short_post_variants",
  "max_chars": 200,
  "variants": [
    {
      "variant_id": "V1",
      "hook": "The biggest AI shift is not smarter models.",
      "body": "It is who can finally afford to ship them.",
      "full_text": "The biggest AI shift is not smarter models. It is who can finally afford to ship them.",
      "angle": "cost_and_access"
    }
  ]
}