solo-content-gen

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/content-gen

/content-gen

Generate a promotion content pack from a project's PRD or README. Produces 3 ready-to-use content pieces: LinkedIn post, Reddit answer draft, and Twitter/X thread. For video scripts, use
/video-promo
.
从项目的PRD或README生成推广内容包,产出3个可直接使用的内容:LinkedIn帖子、Reddit回复草稿和Twitter/X推文线程。如需生成视频脚本,请使用
/video-promo

MCP Tools (use if available)

MCP工具(如有可用请使用)

  • kb_search(query)
    — find related methodology and principles
  • project_info(name)
    — get project details, stack, description
  • project_code_search(query, project)
    — find key features in codebase
If MCP tools are not available, fall back to Glob + Grep + Read.
  • kb_search(query)
    — 查找相关方法论和原则
  • project_info(name)
    — 获取项目详情、技术栈和描述
  • project_code_search(query, project)
    — 在代码库中查找关键功能
如果MCP工具不可用,则退回到Glob + Grep + Read方式。

Steps

步骤

  1. Parse project from
    $ARGUMENTS
    .
    • If project name: find PRD at
      docs/prd.md
      , or README.md, or CLAUDE.md.
    • If path: read directly.
    • If empty: ask via AskUserQuestion — "Which project to generate content for?"
  2. Extract core messaging from PRD/README (parallel reads):
    • Problem: What pain does this solve? (1 sentence)
    • Solution: What does the product do? (1 sentence)
    • ICP: Who is the target user? (persona)
    • Key features: Top 3-5 differentiating features
    • Unique angle: What nobody else does (gap from research.md if exists)
    • Social proof: Any metrics, users, downloads (if available)
  3. Forced reasoning — messaging framework: Before generating content, write out:
    • Hook: What stops the scroll? (pain point or surprising stat)
    • Proof: Why should they believe you? (demo, numbers, authority)
    • CTA: What's the one action? (try, sign up, download)
    • Tone: Based on ICP — casual/professional/technical/friendly
  4. Generate content pieces:

    4a. LinkedIn Post

    Format: Hook line → Story (before/after) → Insight → CTA
    • 1300-1500 chars max
    • First line is the hook (visible before "see more")
    • Use line breaks for readability
    • End with question to drive engagement

    4b. Reddit Answer Draft

    Format: Helpful answer that naturally mentions the product
    • NOT promotional — value-first, product mention is secondary
    • Suggest 3-5 subreddits where this would be relevant
    • Write as if answering someone's genuine question
    • Include "disclaimer: I built this" transparency

    4c. Twitter/X Thread (5-7 tweets)

    Format: Hook tweet → Problem → Solution → Demo → Social proof → CTA
    • Each tweet: 240-280 chars max
    • Tweet 1: standalone hook (works without thread)
    • Last tweet: CTA with link
    • Include emoji sparingly (1-2 per tweet max)
  5. Write content pack to
    docs/content-pack.md
    :
    markdown
    # Content Pack: {Project Name}
    
    **Generated:** {YYYY-MM-DD}
    **ICP:** {target persona}
    **Core message:** {one-line value prop}
    
    ## Messaging Framework
    - **Hook:** {hook}
    - **Proof:** {proof}
    - **CTA:** {cta}
    
    ---
    
    ## 1. LinkedIn Post
    {ready to copy-paste}
    
    ## 2. Reddit Draft
    **Target subreddits:** r/..., r/..., r/...
    {answer draft}
    
    ## 3. Twitter/X Thread
    {numbered tweets}
    
    > For video script, run `/video-promo {project}`.
    
    ---
    *Generated by /content-gen. Edit before publishing.*
  6. Output summary — print core message + list of generated content pieces.
  1. 解析项目:从
    $ARGUMENTS
    中解析。
    • 如果是项目名称:在
      docs/prd.md
      、README.md或CLAUDE.md中查找PRD。
    • 如果是路径:直接读取。
    • 如果为空:通过AskUserQuestion询问——“要为哪个项目生成内容?”
  2. 从PRD/README提取核心信息(并行读取):
    • 问题:该产品解决了什么痛点?(1句话)
    • 解决方案:该产品能做什么?(1句话)
    • ICP(目标客户画像):目标用户是谁?(用户画像)
    • 核心功能:最具差异化的3-5个功能
    • 独特卖点:竞品没有的优势(若有research.md则从中获取差异化信息)
    • 社交证明:相关数据、用户量、下载量(如有)
  3. 强制推理——信息传递框架: 在生成内容前,先明确:
    • 钩子:如何吸引用户停止滑动?(痛点或惊人数据)
    • 佐证:为什么用户要相信你?(演示、数据、权威背书)
    • 行动号召(CTA):希望用户采取什么行动?(试用、注册、下载)
    • 语气:基于ICP确定——随意/专业/技术向/友好
  4. 生成内容片段

    4a. LinkedIn帖子

    格式:钩子语句 → 故事(使用前后对比) → 见解 → CTA
    • 最多1300-1500字符
    • 第一行是钩子(在“查看更多”前可见)
    • 使用换行提升可读性
    • 结尾用问题提升互动性

    4b. Reddit回复草稿

    格式:以有价值的回答自然提及产品
    • 不要硬推广——先提供价值,产品提及为辅
    • 建议3-5个相关的subreddit
    • 以回答真实问题的语气撰写
    • 包含“免责声明:我是该产品的开发者”以保证透明性

    4c. Twitter/X推文线程(5-7条推文)

    格式:钩子推文 → 问题 → 解决方案 → 演示 → 社交证明 → CTA
    • 每条推文最多240-280字符
    • 第一条推文:独立钩子(无需依赖整个线程也能成立)
    • 最后一条推文:带链接的CTA
    • 谨慎使用表情符号(每条推文最多1-2个)
  5. 将内容包写入
    docs/content-pack.md
    markdown
    # Content Pack: {Project Name}
    
    **Generated:** {YYYY-MM-DD}
    **ICP:** {target persona}
    **Core message:** {one-line value prop}
    
    ## Messaging Framework
    - **Hook:** {hook}
    - **Proof:** {proof}
    - **CTA:** {cta}
    
    ---
    
    ## 1. LinkedIn Post
    {ready to copy-paste}
    
    ## 2. Reddit Draft
    **Target subreddits:** r/..., r/..., r/...
    {answer draft}
    
    ## 3. Twitter/X Thread
    {numbered tweets}
    
    > For video script, run `/video-promo {project}`.
    
    ---
    *Generated by /content-gen. Edit before publishing.*
  6. 输出摘要——打印核心信息+已生成内容的列表。

Notes

注意事项

  • All content is draft — always review before publishing
  • Reddit draft should feel genuinely helpful, not promotional
  • For video scripts, use
    /video-promo
    (owns video generation entirely)
  • Rerun after major product updates to refresh messaging
  • Works best with detailed PRD — falls back to README if no PRD
  • 所有内容均为草稿——发布前务必审核
  • Reddit回复草稿要显得真正有帮助,而非硬推广
  • 如需视频脚本,请使用
    /video-promo
    (全权负责视频生成)
  • 产品重大更新后重新运行该工具以更新内容信息
  • 在PRD内容详细时效果最佳——若无PRD则退而求其次使用README

Common Issues

常见问题

No PRD found

未找到PRD

Cause: Project doesn't have
docs/prd.md
or README. Fix: Provide a project path with PRD, or run
/validate
first to generate one.
原因:项目没有
docs/prd.md
或README文件。 解决方法:提供包含PRD的项目路径,或先运行
/validate
生成PRD。

Content too generic

内容过于通用

Cause: PRD lacks specific differentiators or ICP details. Fix: Ensure PRD has detailed problem statement, ICP persona, and unique angle. Add
research.md
for competitive context.
原因:PRD缺乏具体的差异化信息或ICP细节。 解决方法:确保PRD包含详细的问题陈述、ICP用户画像和独特卖点。添加
research.md
提供竞品对比背景。

Wrong tone for audience

内容语气不符合受众

Cause: ICP not clearly defined in PRD. Fix: Specify the target audience in PRD. LinkedIn = professional, Reddit = casual/technical, Twitter = punchy/conversational.
原因:PRD中未明确定义ICP。 解决方法:在PRD中明确目标受众。LinkedIn适合专业语气,Reddit适合随意/技术向语气,Twitter适合简洁/对话式语气。