Creates viral X (Twitter) posts using proven formats, post templates, and creator voice matching. Use when user needs engaging, high-performing posts for X/Twitter.
Generate 3 viral X posts in different proven formats, matched to a creator voice, using battle-tested templates and patterns that drive engagement.
Check $ARGUMENTS first to determine execution mode:
Respond with: "x-writer loaded, proceed with your topic or idea"
Then wait for the user to provide their requirements in the next message.
Proceed immediately to Task Execution (skip the "loaded" message).
When user requirements are available (either from initial $ARGUMENTS or follow-up message):
BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP
Before doing ANYTHING else, you MUST use the Read tool to read ALL three reference files. This is non-negotiable:
Read: ./references/formats.md
Read: ./references/posts.md
Read: ./references/voices.md
What you will find:
DO NOT PROCEED to Step 2 until you have read all three files and have their content in context.
Check if FOUNDER_CONTEXT.md exists in the project root.
From the user's requirements, extract:
Voice Matching Logic:
If the user specified a voice → use that voice directly.
If the user did NOT specify a voice:
Using the formats, posts, and voice you loaded in Steps 1-3:
Critical requirements:
Hard constraints. No interpretation.
Before finalizing ANY post, ask yourself: "Would someone screenshot this and share it with their group chat?" If the answer is no — the post isn't good enough. Rewrite it.
Present exactly 3 posts, each labeled with its format and voice:
## Your 3 X Posts
**Voice:** [Selected voice name]
**Topic:** [User's topic]
---
### Post 1 — [Format Name]
[Full post text, ready to copy and paste]
---
### Post 2 — [Format Name]
[Full post text, ready to copy and paste]
---
### Post 3 — [Format Name]
[Full post text, ready to copy and paste]
Example:
## Your 3 X Posts
**Voice:** Alex Hormozi
**Topic:** Why most SaaS founders fail
---
### Post 1 — Comparison
SaaS founders who fail:
- Build for 6 months in silence
- Launch to crickets
- Blame the market
SaaS founders who win:
- Post the idea before writing code
- Get 50 people to say "I'd pay for that"
- Build only what was validated
The market doesn't lie. Your assumptions do.
---
### Post 2 — One-Liner
The graveyard of failed startups isn't full of bad ideas. It's full of founders who built before they sold.
---
### Post 3 — Stacked Progression
Day 1: "I have a great idea."
Week 2: "The MVP is almost done."
Month 3: "Just a few more features."
Month 6: "Why is no one signing up?"
You shipped a product. You never shipped distribution.
These files MUST be read using the Read tool before generating any posts (see Step 1):
| File | Purpose |
|---|---|
./references/formats.md | 8 proven post formats with structure templates, psychology, and rules |
./references/posts.md | 51+ proven viral posts organized by format — the example library |
./references/voices.md | 7 creator voice profiles (Hormozi, Naval, Gazdecki, Dakota, Machina, Ognjen, Dan Koe) with writing DNA and example posts |
Why all three matter: Formats provide structural templates for how posts are built. Posts show those templates executed at the highest level with real examples. Voices add the human layer that makes content feel authentic instead of AI-generated. All three together = posts that go viral because they have proven structure + proven patterns + authentic voice.
Before finalizing output, verify ALL of the following:
./references/formats.md before generating posts./references/posts.md before generating posts./references/voices.md before generating postsIf ANY check fails → revise before presenting.
Use these unless the user overrides:
Document any assumptions made in the output.