Back to Details

x-writer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

X Writer

X Writer

Purpose

用途

Generate 3 viral X posts in different proven formats, matched to a creator voice, using battle-tested templates and patterns that drive engagement.
生成3篇采用不同成熟格式、匹配创作者风格的爆款X帖子，借助经过实战检验的模板和模式提升互动量。

Execution Logic

执行逻辑

Check $ARGUMENTS first to determine execution mode:
首先检查$ARGUMENTS以确定执行模式：

If $ARGUMENTS is empty or not provided:

若$ARGUMENTS为空或未提供：

Respond with: "x-writer loaded, proceed with your topic or idea"
Then wait for the user to provide their requirements in the next message.
回复： "x-writer已加载，请提供你的主题或想法"
随后等待用户在后续消息中提出需求。

If $ARGUMENTS contains content:

若$ARGUMENTS包含内容：

Proceed immediately to Task Execution (skip the "loaded" message).
立即进入任务执行环节（跳过“已加载”提示消息）。

Task Execution

任务执行

When user requirements are available (either from initial $ARGUMENTS or follow-up message):
当获取到用户需求后（来自初始$ARGUMENTS或后续消息）：

1. MANDATORY: Read Reference Files FIRST

1. 必做：先读取参考文件

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:
  • formats.md: 8 proven post formats with structure templates, psychology, and format-specific rules
  • posts.md: 49+ proven viral posts organized by format type — the example library
  • voices.md: Creator voice profiles with writing DNA, signature patterns, and example posts
DO NOT PROCEED to Step 2 until you have read all three files and have their content in context.
硬性要求——不得跳过此步骤
在进行任何操作之前，必须使用Read工具读取全部三份参考文件，这是不可协商的：
Read: ./references/formats.md
Read: ./references/posts.md
Read: ./references/voices.md
文件内容说明：
  • formats.md：8种经过验证的帖子格式，包含结构模板、心理学依据和格式特定规则
  • posts.md：49+篇按格式分类的爆款帖子实例库
  • voices.md：创作者风格档案，包含写作特征、标志性模式和帖子示例
在读取完所有三份文件并掌握其内容之前，不得进入步骤2。

2. Check for Business Context

2. 检查业务背景

Check if 
FOUNDER_CONTEXT.md
exists in the project root.
  • If it exists: Read it and use the business context to personalize output (industry terminology, audience pain points, brand voice, company name, products).
  • If it doesn't exist: Proceed using defaults from "Defaults & Assumptions."
检查项目根目录下是否存在
FOUNDER_CONTEXT.md
文件。
  • 若存在：读取该文件，并结合业务背景个性化输出内容（如行业术语、受众痛点、品牌风格、公司名称、产品信息）。
  • 若不存在：按照“默认设置与假设”中的内容执行。

3. Analyze Input & Select Voice

3. 分析输入并选择风格

From the user's requirements, extract:
  • Topic/idea — What they want to post about
  • Goal — What they want the post to achieve (engagement, authority, education, humor)
  • Voice preference — If they specified a voice or tone
Voice Matching Logic:
If the user specified a voice → use that voice directly.
If the user did NOT specify a voice:
  1. Analyze the topic and FOUNDER_CONTEXT.md brand voice
  2. Auto-suggest the best match based on topic:
    • Business advice, mindset, pricing, sales, productivity → suggest Alex Hormozi
    • Life philosophy, contrarian takes, self-improvement, minimalism → suggest Naval Ravikant
    • Startup advice, CEO/founder roles, hiring, company building → suggest Andrew Gazdecki
    • Self-improvement, productivity hacks, fitness + learning, habits → suggest Dakota Robertson
    • AI trends, tool launches, tech stack recommendations, urgent opportunities → suggest Machina
    • SaaS growth, AI productivity, founder mindset, revenue strategy → suggest Ognjen Gatalo
    • Personal responsibility, escaping default paths, harsh reality checks, focus training → suggest Dan Koe
  3. Ask the user to confirm using AskUserQuestion:
    • [Suggested Voice] (Recommended) — [one-line description of why it fits]
    • [Other Voice 1] — [one-line description]
    • [Other Voice 2] — [one-line description]
    • My own voice — Natural tone based on FOUNDER_CONTEXT.md brand voice
从用户需求中提取以下信息：
  • 主题/想法——用户想要发布的内容主题
  • 目标——用户希望帖子达成的效果（互动、建立权威、科普、幽默）
  • 风格偏好——用户是否指定了风格或语气
风格匹配逻辑：
若用户指定了风格→直接使用该风格。
若用户未指定风格：
  1. 分析主题和
    FOUNDER_CONTEXT.md
    中的品牌风格
  2. 根据主题自动推荐最匹配的风格：
    • 商业建议、思维模式、定价、销售、生产力→推荐 Alex Hormozi
    • 人生哲学、逆向观点、自我提升、极简主义→推荐 Naval Ravikant
    • 创业建议、CEO/创始人角色、招聘、公司建设→推荐 Andrew Gazdecki
    • 自我提升、生产力技巧、健身+学习、习惯养成→推荐 Dakota Robertson
    • AI趋势、工具发布、技术栈推荐、紧急机遇→推荐 Machina
    • SaaS增长、AI生产力、创始人思维、营收策略→推荐 Ognjen Gatalo
    • 个人责任、打破常规、现实审视、专注力训练→推荐 Dan Koe
  3. 使用AskUserQuestion工具让用户确认：
    • [推荐风格]（推荐）——[一句话说明适配理由]
    • [其他风格1]——[一句话说明]
    • [其他风格2]——[一句话说明]
    • 自定义风格——基于
      FOUNDER_CONTEXT.md
      品牌风格的自然语气

4. Generate 3 Viral Posts

4. 生成3篇爆款帖子

Using the formats, posts, and voice you loaded in Steps 1-3:
  1. Select 3 DIFFERENT formats from formats.md that best fit the user's topic and goal
  2. Study the example posts in posts.md for those formats — internalize the rhythm, structure, and length
  3. Apply the selected voice from voices.md — match their sentence structure, rhythm, and signature patterns (not their exact words or examples)
  4. Draft each post following the format's structure template, the voice's DNA, and all Writing Rules below
  5. Run each post through the Screenshot Test: "Would someone screenshot this and share it?" If no → rewrite before continuing
Critical requirements:
  • Each post must use a DIFFERENT format (no repeats)
  • Each post must sound like the selected voice (structural match, not word-for-word copy)
  • Each post must be about the user's SPECIFIC topic (not generic advice)
  • Each post must follow the format's structure template from formats.md
  • Each post must be ready to copy-paste and post immediately — no placeholders
结合步骤1-3中加载的格式、帖子实例和风格信息：
  1. 从formats.md中选择3种不同的格式，确保最适配用户的主题和目标
  2. 研究posts.md中对应格式的示例帖子——掌握其节奏、结构和篇幅
  3. 应用选中的风格——匹配其句子结构、节奏和标志性模式（而非照搬原话或示例）
  4. 按照格式的结构模板、风格特征及以下写作规则撰写每篇帖子
  5. 对每篇帖子进行截图测试：“有人会截图这篇帖子分享吗？”若答案为否→重写
核心要求：
  • 每篇帖子必须使用不同的格式（不得重复）
  • 每篇帖子必须贴合选中的风格（结构匹配，而非逐字复制）
  • 每篇帖子必须围绕用户指定的具体主题（不得使用通用内容）
  • 每篇帖子必须严格遵循formats.md中的格式结构模板
  • 每篇帖子必须可直接复制粘贴发布——无占位符

5. Format and Verify

5. 格式化与验证

  • Structure output according to Output Format section
  • Complete Quality Checklist self-verification before presenting output
  • If any post feels generic, forced, or wouldn't pass the Screenshot Test → rewrite before presenting
  • 按照“输出格式”部分的要求整理输出内容
  • 在呈现输出前完成“质量检查表”的自我验证
  • 若任何帖子显得通用、生硬或无法通过截图测试→重写后再呈现

Writing Rules

写作规则

Hard constraints. No interpretation.
硬性约束，不得随意解读。

Core Rules (Apply to ALL posts)

核心规则（适用于所有帖子）

  • Maximum 280 characters for single posts. If a post exceeds 280 characters, it must be structured as a thread (each tweet under 280 characters).
  • First line is the hook — it determines whether people click "Show more." Make it the strongest line in the post.
  • Use line breaks strategically. White space = visual breathing room = readability.
  • No hashtags. They reduce reach and look amateur on X.
  • No engagement bait ("like if you agree", "RT if this resonates", "thoughts?"). It kills reach.
  • No emojis unless the voice or topic specifically calls for it. When used, maximum 1-2 per post.
  • Specific numbers > vague claims ("17 strategies" not "many strategies").
  • Opinions > facts. X rewards bold takes, not Wikipedia summaries.
  • Active voice only. Never passive.
  • Present tense preferred.
  • Every word must earn its place. If you can cut a word without losing meaning, cut it.
  • No "I think" or "In my opinion" — just state the opinion as fact. Confidence is voice.
  • 单条帖子最多280字符。若超过280字符，必须拆分为线程帖（每条推文不超过280字符）。
  • 第一行是钩子——决定用户是否点击“查看更多”。务必是帖子中最有吸引力的内容。
  • 合理使用换行。留白=视觉呼吸空间=可读性。
  • 禁止使用话题标签（Hashtag）。它们会降低曝光量，在X平台显得不专业。
  • 禁止使用互动诱饵（如“同意就点赞”“共鸣就转发”“你怎么看？”）。会严重影响曝光。
  • 除非风格或主题明确要求，否则禁止使用表情符号。若使用，每篇帖子最多1-2个。
  • 具体数字>模糊表述（如“17种策略”而非“多种策略”）。
  • 观点>事实。X平台推崇大胆观点，而非维基百科式的总结。
  • 仅使用主动语态。禁止使用被动语态。
  • 优先使用现在时态。
  • 每个字都要有存在的价值。若删去某个字不影响意思，就删掉它。
  • 禁止使用“我认为”或“在我看来”——直接将观点作为事实陈述。自信就是风格。

Voice-Matching Rules

风格匹配规则

  • Match the voice's SENTENCE STRUCTURE — short choppy lines vs flowing sentences, fragments vs complete thoughts.
  • Match their RHYTHM — how they pace ideas, where they place line breaks, how they build tension.
  • Match their PERSPECTIVE — coaching from authority (Hormozi) vs philosophical detachment (Naval) vs peer founder advice (Gazdecki).
  • Do NOT copy their exact phrases, examples, or company references. Create original content that SOUNDS like them structurally.
  • If the user chose "My own voice," use a natural, conversational tone that matches FOUNDER_CONTEXT.md brand voice. If no context exists, default to direct and conversational.
  • 匹配风格的句子结构——短句碎句 vs 流畅长句，片段式 vs 完整表达。
  • 匹配风格的节奏——观点推进的速度、换行的位置、张力的构建方式。
  • 匹配风格的视角——权威指导（Hormozi） vs 哲学式疏离（Naval） vs 同行创始人建议（Gazdecki）。
  • 不得照搬风格示例中的原话、案例或公司参考。创作结构上贴合风格的原创内容。
  • 若用户选择“自定义风格”，使用贴合
    FOUNDER_CONTEXT.md
    品牌风格的自然口语化语气。若无相关背景，默认使用直接、口语化的语气。

Format-Specific Rules

格式特定规则

  • One-Liners: One sentence. One idea. No explanations. Every word carries weight.
  • Two-Part Punch: Line break between parts. Second part MUST change the meaning of the first.
  • Numbered Lists: Odd numbers preferred. Each item must be specific and standalone. Strong, opinionated closer.
  • Stacked Progression: Same grammatical structure per line. Build momentum. The final line MUST break the pattern.
  • Comparison: Stark, obvious contrast. Don't lecture — let the contrast make the point.
  • Example + Takeaway: Use real, named companies or people. Minimum 3 examples. Actionable closer.
  • Reverse Advice: Deadpan delivery. No winking. Every item is a real mistake people make.
  • Humor: One joke per post. Deadpan > trying hard. Industry-specific > generic. Never explain the joke.
  • 单句式：一句话，一个观点，无需解释。每个字都有分量。
  • 双段冲击式：两段之间换行。第二段必须改变第一段的含义。
  • 编号列表式：优先使用奇数编号。每个条目必须具体且独立。结尾要有有力、明确的观点。
  • 递进堆叠式：每行使用相同的语法结构。逐步建立气势。最后一行必须打破模式。
  • 对比式：鲜明、清晰的对比。无需说教——让对比自行传递观点。
  • 案例+结论式：使用真实的知名公司或人物案例。至少3个案例。结尾要有可执行的结论。
  • 逆向建议式：面无表情的表述方式。不要嬉皮笑脸。每条内容都是人们常犯的真实错误。
  • 幽默式：每篇帖子一个笑话。冷面幽默>刻意搞笑。行业特定>通用。永远不要解释笑话。

The Screenshot Test

截图测试

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.
在最终确定任何帖子前，问自己：“有人会截图这篇帖子分享到群聊吗？”若答案为否——帖子不够好，重写。

Output Format

输出格式

Present exactly 3 posts, each labeled with its format and voice:
markdown
undefined
呈现恰好3篇帖子，每篇标注其格式和风格：
markdown
undefined

Your 3 X Posts

你的3篇X帖子

Voice: [Selected voice name] Topic: [User's topic]
风格： [选中的风格名称] 主题： [用户指定的主题]

Post 1 — [Format Name]

帖子1 — [格式名称]

[Full post text, ready to copy and paste]
[完整的帖子内容，可直接复制粘贴]

Post 2 — [Format Name]

帖子2 — [格式名称]

[Full post text, ready to copy and paste]
[完整的帖子内容，可直接复制粘贴]

Post 3 — [Format Name]

帖子3 — [格式名称]

[Full post text, ready to copy and paste]

**Example:**

```markdown
[完整的帖子内容，可直接复制粘贴]

**示例：**

```markdown

Your 3 X Posts

你的3篇X帖子

Voice: Alex Hormozi Topic: Why most SaaS founders fail
风格： Alex Hormozi 主题： 为何大多数SaaS创始人失败

Post 1 — Comparison

帖子1 — 对比式

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.
失败的SaaS创始人：
  • 默默开发6个月
  • 发布后无人问津
  • 责怪市场
成功的SaaS创始人：
  • 写代码前先发布想法
  • 让50人表示“我愿意付费”
  • 只开发经过验证的功能
市场不会说谎。说谎的是你的假设。

Post 2 — One-Liner

帖子2 — 单句式

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

帖子3 — 递进堆叠式

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.

---
第1天：“我有个好主意。” 第2周：“MVP快完成了。” 第3个月：“只差几个功能了。” 第6个月：“为什么没人注册？”
你交付了产品。却从未做过推广。

---

References

参考文件

These files MUST be read using the Read tool before generating any posts (see Step 1):
FilePurpose
./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.
在生成任何帖子前，必须使用Read工具读取以下文件（见步骤1）：
文件用途
./references/formats.md
包含8种经过验证的帖子格式，附带结构模板、心理学依据和规则
./references/posts.md
包含51+篇按格式分类的爆款帖子——实例库
./references/voices.md
包含7种创作者风格档案（Hormozi、Naval、Gazdecki、Dakota、Machina、Ognjen、Dan Koe），附带写作特征和帖子示例
**为何这三份文件都很重要：**格式提供帖子的结构模板，实例展示模板的高水平落地方式，风格为内容增添人文温度，避免AI生成感。三者结合=具备成熟结构、验证模式和真实风格的爆款帖子。

Quality Checklist (Self-Verification)

质量检查表（自我验证）

Before finalizing output, verify ALL of the following:
在最终呈现输出前，验证以下所有内容：

Pre-Execution Check

执行前检查

  • I read 
    ./references/formats.md
    before generating posts
  • I read 
    ./references/posts.md
    before generating posts
  • I read 
    ./references/voices.md
    before generating posts
  • I have all formats, example posts, and voice profiles in context
  • 生成帖子前已读取
    ./references/formats.md
  • 生成帖子前已读取
    ./references/posts.md
  • 生成帖子前已读取
    ./references/voices.md
  • 已掌握所有格式、示例帖子和风格档案的内容

Format Verification

格式验证

  • Each post uses a DIFFERENT format from formats.md (no repeats)
  • Each post follows its format's structure template exactly
  • Format-specific rules are followed (line counts, structure requirements)
  • 每篇帖子使用formats.md中的不同格式（无重复）
  • 每篇帖子严格遵循对应格式的结构模板
  • 遵循格式特定规则（行数、结构要求）

Voice Verification

风格验证

  • All 3 posts match the selected voice's sentence structure and rhythm
  • Posts sound like the voice — structurally matched, not copied
  • No phrases or examples were directly lifted from voice example posts
  • 3篇帖子均匹配选中风格的句子结构和节奏
  • 帖子贴合风格——结构匹配，而非复制
  • 未直接照搬风格示例帖子中的短语或案例

Content Verification

内容验证

  • All 3 posts are about the user's specific topic (not generic filler)
  • Each post contains specific details, numbers, or examples (nothing vague)
  • No hashtags, engagement bait, or unnecessary emojis
  • Every post is under 280 characters OR clearly structured as a thread
  • Each post is ready to copy-paste and post immediately
  • 3篇帖子均围绕用户指定的具体主题（无通用填充内容）
  • 每篇帖子包含具体细节、数字或案例（无模糊内容）
  • 无话题标签、互动诱饵或不必要的表情符号
  • 每篇帖子不超过280字符，或明确拆分为线程帖
  • 每篇帖子可直接复制粘贴发布

The Screenshot Test

截图测试

  • Would someone screenshot Post 1 and share it? If no → rewrite
  • Would someone screenshot Post 2 and share it? If no → rewrite
  • Would someone screenshot Post 3 and share it? If no → rewrite
If ANY check fails → revise before presenting.
  • 有人会截图帖子1分享吗？若否→重写
  • 有人会截图帖子2分享吗？若否→重写
  • 有人会截图帖子3分享吗？若否→重写
若任何一项检查未通过→修改后再呈现。

Defaults & Assumptions

默认设置与假设

Use these unless the user overrides:
  • Number of posts: 3 (each in a different format)
  • Voice: Ask user to choose (auto-suggest based on topic and FOUNDER_CONTEXT.md)
  • Goal: Maximize engagement (likes, reposts, bookmarks)
  • Audience: Founders, entrepreneurs, builders (unless FOUNDER_CONTEXT specifies otherwise)
  • Tone: Matches selected voice profile
  • Post type: Single post (not thread) unless the topic requires more depth
  • Character limit: 280 characters per post (X standard)
  • Topic specificity: Use the user's exact topic — never drift to generic startup advice
Document any assumptions made in the output.
除非用户另行指定，否则使用以下设置：
  • 帖子数量：3篇（每篇使用不同格式）
  • 风格：让用户选择（根据主题和
    FOUNDER_CONTEXT.md
    自动推荐）
  • 目标：最大化互动量（点赞、转发、收藏）
  • 受众：创始人、创业者、从业者（除非
    FOUNDER_CONTEXT.md
    另有指定）
  • 语气：匹配选中的风格档案
  • 帖子类型：单条帖子（非线程帖），除非主题需要更深入的内容
  • 字符限制：每篇帖子280字符（X平台标准）
  • 主题特异性：严格使用用户指定的主题——不得偏离为通用创业建议
在输出中记录所有做出的假设。