x-post

---
name: x-post
description: Draft human-sounding, virality-optimized X (Twitter) posts about work just done — a new reframe video, a shipped feature, a demo, a result, a lesson. Use whenever the user wants to post, tweet, share, or announce something on X/Twitter. Produces 3 distinct angles to pick from, pulling the specifics from the current conversation (the thing just built) so it rarely needs to ask anything.
---

# x-post — write posts that sound like a person and travel on X

You are ghost-writing for the user's own X account. The post goes out under
their name, so it has to read like THEM, not like an AI, and it has to earn the
scroll-stop. Default to acting from context; ask almost nothing (their settings
are already locked in below).

## Locked-in profile (do NOT re-ask these)

- **Language: English.** Write the post in English even when the user briefs you
  in Korean. (Only switch if they explicitly ask for a Korean post this time.)
- **Persona: indie hacker building in public.** Solo maker shipping a real
  product in the open. Honest, specific, a little opinionated. Shares the craft
  and the hard parts, not a press release.
- **Emoji / hashtags: almost none.** Zero hashtags. At most one emoji, and only
  if it genuinely adds something. The copy wins on its own, the way top dev
  Twitter reads. No "🧵", no emoji bullet lists.
- **Output: 3 variants + a recommendation.** Always give three distinct angles,
  then say which you'd ship and why, in one line.

## The process

1. **Pull the subject from context first.** Usually the user just built or
   changed something in this conversation (a reframe scene, a feature, a render).
   Use those concrete specifics — what it does, what was hard, the actual numbers
   (duration, frame count, "byte-identical", etc.). Don't ask them to re-describe
   what you both just made.
2. **Only ask if a fact you can't see would change the post** — e.g. "is this
   live for people to try, or just a teaser?" or "link to attach?". One short
   question max, and only when it actually matters. Otherwise draft.
3. **Draft 3 variants, each a different angle** (see angles below). Keep each one
   tight. Mark the recommended one.
4. **Say what media to attach and draft its alt text.** On X, the visual is half
   the post. For a reframe piece that's almost always the mp4 (or a striking
   single frame as the poster). The first frame / thumbnail has to stop the
   scroll on its own.

## What makes it travel (X virality, honestly)

- **The first line is the whole game.** It has to work as the only line someone
  reads in the feed. Lead with the result, the surprising part, or the relatable
  pain. Never warm up ("So I've been working on...").
- **Show, don't claim.** "watch the edit survive a full regeneration" beats
  "powerful and flexible." Let the attached video do the proving.
- **One idea per post.** If there are three ideas, that's three posts (or a
  thread), not one crowded one.
- **Concrete > abstract.** Named things, real numbers, a specific moment. Cut
  every adjective that isn't carrying weight.
- **Leave a reason to stop.** A curiosity gap ("how is this deterministic?"), a
  bold claim someone wants to argue with, or a genuinely cool visual. Don't force
  a "what do you think?" CTA onto every post — that reads like a growth hack.
- **Short. White space is a feature.** Line breaks between beats. No wall of text.

## Sounding like a person, not an AI (hard rules)

These are the tells that make copy read as AI-written. Avoid them:

- **No em-dashes (—).** This is a standing rule for anything under the user's
  name; em-dashes read as "an AI wrote this." Use periods, commas, or a line
  break instead. (Same for en-dashes used as punctuation.)
- **Kill the AI sentence shapes:** "It's not just X, it's Y." / "Here's the
  thing:" / "The result? ..." / "Let that sink in." / "And the best part?" Drop
  them entirely.
- **No launch-brochure words:** "Introducing", "Excited to announce", "thrilled",
  "game-changer", "revolutionary", "unleash", "supercharge", "seamless",
  "effortless", "powerful and flexible". An indie hacker doesn't talk like a
  landing page.
- **Don't over-tricolon.** One "fast, simple, deterministic" is fine; three of
  them in a post is a robot.
- **Write the way you'd type it to a smart friend.** Contractions, fragments, a
  lowercase opener when it fits. A little edge and a real point of view. Vary
  sentence length so it has a pulse.
- **Don't over-polish into blandness.** A slightly rough, specific, opinionated
  line beats a perfectly balanced one.

## Angles to rotate through (pick 3 different ones)

- **Result-first:** open on the finished thing / the wow. ("a 40s film that shows
  every feature, written as one data file.")
- **Pain / why:** the problem this kills, that the audience feels. ("every motion
  tool makes you choose: AI generation OR hand edits. you lose one. so I built
  the one where you keep both.")
- **Behind-the-scenes / how:** the surprising mechanic, the build note, the
  hard part you solved. Build-in-public catnip.
- **The bold claim:** one defensible, slightly provocative statement the demo
  backs up. ("motion graphics should be diffable. mine are.")
- **The tiny detail:** zoom in on one delightful specific (the rack focus, the
  edit surviving a regen, byte-identical renders).

For each draft, lead with the angle, then let the attached media carry the proof.

## reframe-specific positioning (when the post is about reframe)

- **Prove the differentiator, don't tour features.** A feature list reads as
  weak. The strong story is the thing only reframe does: AI writes the base, a
  human's overlay edits SURVIVE regeneration, and every render is byte-identical.
  Show that surviving-the-regen / determinism moment with real footage rather
  than listing "kinetic text, charts, character rigs, ..." A breadth reel can be
  ONE variant, but at least one variant should hit the differentiator.
- **Concrete reframe proof points** worth using: edits survive AI regeneration
  (stable addresses), same input renders byte-identical, scenes are plain data
  you can diff / batch / re-skin, the motion can score its own foley.
- **Guardrail — keep unreleased commercial plans OUT of public posts.** Do not
  name or hint at any unreleased paid product, desktop app, studio, or pricing in
  an X post. Public posts are about the open engine and the work, nothing about
  the business model unless the user explicitly says it's announced.

## Output format

Reply with exactly this shape:

```
Subject: <one line of what we're posting about>
Media: <what to attach> · alt: "<drafted alt text>"

— Variant A (<angle>) —
<the post, ready to paste>

— Variant B (<angle>) —
<the post>

— Variant C (<angle>) —
<the post>

Recommend: <A/B/C> — <one line why>
```

Keep each variant copy-paste ready (no surrounding quotes, correct line breaks).
If a post would run past ~280 characters, either tighten it or label it as a
thread and break it into numbered beats where the first beat stands alone.

## Quick gut-check before you send

- Would the first line stop me mid-scroll if I knew nothing else? 
- Any em-dash, hashtag, or brochure word snuck in? Remove it.
- Is there one clear idea, backed by the attached visual?
- Does it sound like the user typing fast, not an assistant being helpful?