X Longform Post

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%

Formatting for X

• X articles support markdown-like formatting in long posts
• Use code blocks (```) for ASCII art — they render in monospace on X
• Bold with asterisks where supported
• Keep paragraphs to 1-3 sentences max
• Line breaks between every thought

Content Sources

Pull from real data whenever possible:

• Real metrics from your business
• Specific incidents and debugging stories
• Actual decisions made and why

Never fabricate metrics. Use real numbers or don't use numbers.

Analytics Feedback Loop

If X/Twitter analytics are available, use them before drafting and after publishing.

Before drafting:

• Pull recent post performance for similar topics and formats.
• Compare impressions, engagement rate, replies, reposts, bookmarks, profile clicks, follower delta, post length, hook style, proof number, CTA type, and topic bucket.
• Prefer hooks and structures that have actually worked. Do not worship cleverness. Cleverness without distribution is theater with better fonts.

After publishing:

1. Log post URL/id, publish time, hook, title, proof number, structure, CTA, and topic bucket.
2. Pull analytics after the readback window.
3. Compare against a baseline cohort of similar posts.
4. Patch the title formulas, hook patterns, CTA rules, or section structure only if the candidate beats baseline or produces a clearly better audience signal.

Judgment metrics:

• impressions
• engagement rate
• replies
• reposts
• bookmarks
• profile clicks
• follower delta
• quality of replies

Every promoted format change should include a baseline window, candidate window, metric winner, caveats, and rollback rule.

Input Format

User provides:

• Topic: What the post is about
• Angle: The contrarian or unique framing
• Source material: Real examples, data, incidents (optional)

Output

Deliver the complete post ready to paste into X. No preamble, no "here's your post" — just the post itself.

If the post would work better as a thread (>1500 chars), split into numbered tweets with each one standalone valuable.

Reference

See references/founder-voice.md for extended voice examples and patterns. Customize with your founder's real voice.