x-longform-post

name	x-longform-post
description	Write long-form X (Twitter) posts and threads in a founder/CEO voice. Use when drafting X articles, long tweets, thought leadership threads, or viral content. Produces contrarian, data-backed posts with ASCII diagrams and code block visuals. Includes mandatory AI humanizer pass (24-pattern detector) before finalizing.
version	1.0.1
display_name	x-longform-post
display_name_en	X Longform Post
description_zh	撰写 X(Twitter) 长文，创始人语气 + AI 去味检测
description_en	Write long-form X posts in founder voice with AI humanizer detection
visibility	public

X Long-Form Post Writer

Write posts for X in your founder/CEO's authentic voice. Every post should feel like a real person wrote it — not a content team, not a bot.

See references/founder-voice.md for the founder voice template. Customize it with your founder's real patterns.

---

Voice Rules

• Simple declarative sentences. Short paragraphs.
• Contrarian angles backed by specific numbers and real examples.
• No corporate speak. No "I'm excited to share." No emoji in body text.
• Open with a hook that stops the scroll — contrarian claim, surprising number, or uncomfortable truth.
• End with a payoff: uncomfortable truth → "worth it" resolution.

---

Structure

1. Hook (1-2 lines) — Contrarian claim or surprising stat
2. Setup (2-3 lines) — Establish credibility/context fast
3. Sections — Each follows: problem → what actually happened → fix/lesson
4. ASCII diagram — At least one per post (see below)
5. Uncomfortable truth — The insight most people avoid
6. Payoff — Was it worth it? Yes, and here's why.

---

ASCII Diagrams (MANDATORY)

Every post MUST include at least one ASCII diagram in a code block. These break up walls of text and make complex systems visual.

Use box-drawing characters:

┌─────────┐    ┌─────────┐    ┌─────────┐
│  Input  │───►│ Process │───►│ Output  │
└─────────┘    └─────────┘    └─────────┘

Diagram types to use:

• System architecture — boxes connected by arrows showing how components relate
• Before/after — side-by-side comparison of old vs new state
• Flow diagrams — decision trees, pipelines, sequences
• Hierarchy — org charts, priority stacks, dependency trees
• Metrics — simple bar charts using block characters (█ ▓ ░)

Keep diagrams:

• Under 40 chars wide (mobile rendering)
• Simple enough to parse in 3 seconds
• Labeled clearly — no ambiguous boxes

Example — system flow:

Input (60s)
    │
    ▼
┌──────────┐
│ Process  │ step 1
└────┬─────┘
     ▼
┌──────────┐
│ Dispatch │ step 2
└────┬─────┘
     ▼
  Output

Example — metrics visualization:

Performance by Category:
Category A   ████████████ 100%
Category B   ████████░░░░  67%
Category C   ░░░░░░░░░░░░   0%