social-media-posts
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSocial Media Post Generator
社交媒体帖子生成工具
Create platform-specific social media posts that respect each platform's conventions, character limits, and audience expectations. Produces copy-paste-ready content.
创建符合各平台规则、字符限制和受众预期的平台专属社交媒体帖子，生成的内容可直接复制粘贴使用。
Modes
生成模式
From Scratch
从零创建
User provides topic + key points. Generate posts for selected platforms.
用户提供主题+关键点，为选定平台生成帖子。
From Content
基于现有内容改编
User provides existing content (blog post, newsletter, announcement, press release). Repurpose into platform-appropriate posts.
用户提供现有内容（博客文章、通讯、公告、新闻稿），将其改编为适配平台的帖子。
Campaign
营销活动模式
Generate a coordinated set of posts across all platforms for a single launch, announcement, or event. Includes posting sequence and timing suggestions.
为单次发布、公告或活动生成跨平台的协调帖子集合，包含发布顺序和时间建议。
Workflow
工作流程
1. Gather Input
1. 收集输入信息
| Field | Required | Example |
|---|---|---|
| Topic or source content | Yes | "We just launched a new feature" or path to blog post |
| Target platforms | Yes | LinkedIn, Facebook, Instagram, Reddit |
| Tone | No | Professional, casual, enthusiastic, educational |
| CTA | No | "Try it free", "Read more", "Comment your thoughts" |
| Link to include | No | https://example.com/blog/new-feature |
| Image available? | No | Yes/no — affects post structure |
If the user provides a file path or URL to existing content, read it first and extract the key messages.
| 字段 | 是否必填 | 示例 |
|---|---|---|
| 主题或源内容 | 是 | "我们刚刚推出了一项新功能" 或博客文章链接 |
| 目标平台 | 是 | LinkedIn, Facebook, Instagram, Reddit |
| 语气 | 否 | 专业、随意、热情、科普 |
| 行动号召（CTA） | 否 | "免费试用"、"阅读更多"、"分享你的想法" |
| 需包含的链接 | 否 | https://example.com/blog/new-feature |
| 是否有可用图片 | 否 | 是/否 — 影响帖子结构 |
如果用户提供现有内容的文件路径或URL，需先读取内容并提取核心信息。
2. Generate Per-Platform Posts
2. 生成各平台专属帖子
Audience: Professionals, B2B, industry peers
Tone: Authoritative but approachable, thought-leadership
Optimal length: 1,200–1,500 characters (longer posts perform well)
Structure:
[Hook line — must grab attention before "see more" truncation]
[blank line]
[2-3 short paragraphs with line breaks between]
[blank line]
[CTA or question to drive comments]
[blank line]
[3-5 relevant hashtags]Rules:
- Hook must work in first 2 lines (before "…see more" at ~210 chars)
- Use line breaks liberally — wall-of-text kills engagement
- Ask a question at the end to drive comments
- Hashtags: 3-5 max, mix broad (#Marketing) and niche (#CloudflareWorkers)
- Links in comments perform better than in post body (algorithm penalty)
- No emoji overload — 1-2 max, or none for serious topics
Image specs: 1200×627px (1.91:1) for link preview, or 1080×1080 (1:1) for standalone
Example:
We just shipped something we've been building for 6 months.
It started as a "wouldn't it be nice if…" conversation and turned
into our most requested feature. Here's what we learned:
→ Users don't want more features. They want fewer clicks.
→ The prototype we almost killed became the final product.
→ Shipping weekly forced us to cut scope ruthlessly.
The full story is in our latest blog post (link in comments).
What's the hardest product decision you've made this year?
#ProductDevelopment #StartupLife #BuildInPublic受众：职场人士、B2B从业者、行业同行
语气：权威且亲和，主打思想领导力
最佳长度：1200–1500字符（长帖表现更佳）
结构:
[钩子内容 — 必须在“查看更多”截断前抓住用户注意力]
[空行]
[2-3个短段落，段落间空行]
[空行]
[行动号召或引发评论的问题]
[空行]
[3-5个相关话题标签]规则:
- 钩子内容必须在前两行有效（约210字符处会触发“…查看更多”）
- 大量使用换行 — 大段文字会降低互动率
- 在结尾提出问题以促进评论
- 话题标签：最多3-5个，混合宽泛标签（#Marketing）和细分标签（#CloudflareWorkers）
- 链接放在评论中比放在帖子正文中表现更好（算法会对正文链接降权）
- 不要过度使用表情符号 — 最多1-2个，严肃话题可完全不用
图片规格：链接预览图1200×627px（1.91:1），独立图片1080×1080（1:1）
示例:
我们耗时6个月打造的功能终于上线了。
最初这只是一句“如果能这样做就好了”的闲聊，后来却成了用户呼声最高的功能。下面是我们的收获：
→ 用户不需要更多功能，他们需要更少的操作步骤。
→ 我们差点砍掉的原型最终成了正式产品。
→ 每周迭代的节奏迫使我们果断缩减功能范围。
完整故事请查看我们最新的博客文章（链接在评论区）。
今年你做过最艰难的产品决策是什么？
#ProductDevelopment #StartupLife #BuildInPublicAudience: Mixed — friends, family, community, local businesses
Tone: Conversational, warm, community-focused
Optimal length: 80–150 characters for engagement, up to 500 for storytelling
Structure:
[Opening hook — conversational, relatable]
[1-2 short paragraphs]
[Link (if applicable) — Facebook generates preview cards]
[Engagement prompt — question or poll]Rules:
- Link posts: Facebook auto-generates a preview card — don't repeat the headline in your text
- Short posts (under 130 chars) get larger text rendering in feed
- Questions and polls drive highest engagement
- Tag relevant pages when mentioning partners/clients
- Hashtags: 1-3 or none — Facebook hashtags are less effective than other platforms
- Emojis are welcome but don't overdo (2-3 max)
Image specs: 1200×630px (1.91:1) for link preview, 1080×1080 (1:1) for photo posts
Example:
6 months ago we started building something our users kept asking for.
Today it's live. 🚀
We wrote up the full story — the pivots, the almost-killed prototype,
and why "fewer clicks" won over "more features."
[link]
What feature have you shipped that surprised you?受众：混合群体 — 朋友、家人、社区成员、本地商家
语气：口语化、亲切、注重社区互动
最佳长度：80–150字符（互动率最高），叙事类帖子最长可达500字符
结构:
[开场钩子 — 口语化、有共鸣]
[1-2个短段落]
[链接（如有） — Facebook会自动生成预览卡片]
[互动提示 — 问题或投票]规则:
- 链接帖子：Facebook会自动生成预览卡片 — 不要在正文中重复标题
- 短帖（130字符以内）在信息流中会以更大字号展示
- 问题和投票能带来最高的互动率
- 提及合作伙伴/客户时标记相关主页
- 话题标签：1-3个或完全不用 — Facebook的话题标签效果远不如其他平台
- 可使用表情符号但不要过度（最多2-3个）
图片规格：链接预览图1200×630px（1.91:1），图片帖1080×1080（1:1）
示例:
6个月前，我们开始打造用户反复请求的功能。
今天它终于上线了。🚀
我们写下了完整的故事 — 包括中途的转向、差点被砍掉的原型，以及为什么“更少操作”战胜了“更多功能”。
[链接]
你上线过哪些让自己意外的功能？Audience: Visual-first, younger demographic, lifestyle/brand-focused
Tone: Authentic, visual storytelling, personality-forward
Optimal length: Key message in first 125 chars (truncation point), full caption up to 2,200
Structure:
[First line — must work as standalone (before "…more")]
[blank line]
[Story or detail — 2-4 short paragraphs]
[blank line]
[CTA — save, share, comment, link in bio]
.
.
.
[Hashtags — in first comment OR separated by dots]Rules:
- First 125 characters must carry the message (everything after is hidden behind "…more")
- No clickable links in captions — direct to "link in bio"
- Hashtags: 20-30 in first comment (not in caption) for discoverability
- Mix hashtag sizes: 5 large (1M+ posts), 10 medium (100K-1M), 10 niche (<100K)
- Emojis are part of the language — use them naturally
- Carousel posts: include a swipe CTA ("Swipe for the full breakdown →")
- Stories: prompt action ("Reply with 🔥 if you relate")
Image specs: 1080×1080 (1:1) feed, 1080×1350 (4:5) portrait, 1080×1920 (9:16) stories/reels
Example:
We shipped our most requested feature today. Here's the story 👇
Six months ago, someone on our team said "wouldn't it be nice
if users could do this in one click instead of five?"
We almost killed the prototype twice. But our users kept asking
for it. So we shipped it.
The biggest lesson? Your users don't want more features.
They want fewer clicks.
Full story → link in bio
💬 What's one feature you wish was simpler in your favourite app?First comment:
#ProductLaunch #StartupLife #BuildInPublic #TechStartup
#ProductDevelopment #UXDesign #SaaS #FeatureLaunch
[... 20-30 total hashtags]受众：视觉优先、年轻群体、注重生活方式/品牌调性
语气：真实、视觉叙事、突出个性
最佳长度：核心信息放在前125字符（截断点），完整标题最长可达2200字符
结构:
[第一行 — 需能独立传达核心信息（在“…查看更多”截断前）]
[空行]
[故事或细节 — 2-4个短段落]
[空行]
[行动号召 — 收藏、分享、评论、查看简介链接]
.
.
.
[话题标签 — 放在第一条评论中或用点号分隔]规则:
- 前125字符必须承载核心信息（之后的内容会被隐藏在“…查看更多”后）
- 正文中不能放可点击链接 — 引导用户查看“简介链接”
- 话题标签：在第一条评论中放20-30个（不要放在正文中）以提升曝光
- 混合不同量级的标签：5个大标签（100万+帖子）、10个中标签（10万-100万）、10个细分标签（10万以下）
- 表情符号是常用表达 — 自然使用即可
- 轮播帖：加入滑动提示（“滑动查看完整解析 →”）
- 快拍：引导互动（“如果你有同感就回复🔥”）
图片规格：信息流帖1080×1080（1:1），竖版帖1080×1350（4:5），快拍/短视频1080×1920（9:16）
示例:
我们今天上线了用户呼声最高的功能。背后的故事👇
六个月前，团队里有人说“如果用户能一键完成这个操作而不是五步就好了？”
我们两次差点砍掉这个原型。但用户一直在请求，所以我们还是上线了。
最大的教训是什么？用户不需要更多功能，他们需要更少的操作步骤。
完整故事 → 查看简介链接
💬 你希望常用APP里哪项功能能更简单？第一条评论:
#ProductLaunch #StartupLife #BuildInPublic #TechStartup
#ProductDevelopment #UXDesign #SaaS #FeatureLaunch
[... 共20-30个话题标签]Audience: Community-specific, values authenticity, allergic to marketing
Tone: Genuine, value-first, conversational, never salesy
Optimal length: Title 100-150 chars, body varies by subreddit
Structure:
Title: [Descriptive, value-focused — NOT clickbait]
Body:
[Context — why this matters to this community]
[The substance — what you learned, built, or discovered]
[Optional: link to more detail]
[Discussion prompt — genuine question]Rules:
- Title is everything — Reddit lives and dies by titles
- NO self-promotion feel — lead with value, not product
- Each subreddit has different norms — check the rules before posting
- Don't use hashtags (not a Reddit convention)
- Don't use emojis in titles (feels out of place on most subreddits)
- Share the insight, not the product. "Here's what we learned" > "Check out our new feature"
- Cross-posting: adapt tone per subreddit (r/startups vs r/webdev vs r/smallbusiness)
Subreddit suggestions by topic:
| Topic | Subreddits |
|---|---|
| Product launch | r/SideProject, r/startups, r/indiehackers |
| Web dev | r/webdev, r/javascript, r/reactjs |
| Design | r/web_design, r/UI_Design |
| Business | r/smallbusiness, r/Entrepreneur |
| Tech | r/programming, r/technology |
Example:
Title: After 6 months of building, the biggest lesson was
"users want fewer clicks, not more features"
We built a feature our users kept requesting. Halfway through
we almost killed it because the prototype felt clunky.
What saved it: we stopped adding capabilities and started
removing steps. The final version does less than the prototype
but users complete the task in 1 click instead of 5.
Three things I'd tell past-me:
1. Prototype with your heaviest users, not your most vocal ones
2. "Ship weekly" forces you to cut scope — that's a feature
3. The thing users ask for and the thing they need are different
Anyone else had a similar experience where removing features
improved the product?受众：社区专属、重视真实性、反感营销话术
语气：真诚、价值优先、口语化、绝对不能有推销感
最佳长度：标题100-150字符，正文长度因子版块而异
结构:
标题: [描述性、价值导向 — 绝对不能是标题党]
正文:
[背景 — 为什么这对该社区重要]
[核心内容 — 你学到的、打造的或发现的东西]
[可选：更多细节链接]
[讨论提示 — 真诚的问题]规则:
- 标题决定一切 — Reddit的流量完全依赖标题
- 绝对不能有自我推销感 — 先提供价值，再提及产品
- 每个子版块有不同规则 — 发帖前先查看版块规则
- 不要使用话题标签（不符合Reddit惯例）
- 标题中不要使用表情符号（在大多数子版块中会显得格格不入）
- 分享见解，而非产品。“这是我们学到的”远好于“看看我们的新功能”
- 跨版块发帖：根据子版块调整语气（如r/startups vs r/webdev vs r/smallbusiness）
按话题推荐子版块:
| 话题 | 子版块 |
|---|---|
| 产品发布 | r/SideProject, r/startups, r/indiehackers |
| 网页开发 | r/webdev, r/javascript, r/reactjs |
| 设计 | r/web_design, r/UI_Design |
| 商业 | r/smallbusiness, r/Entrepreneur |
| 科技 | r/programming, r/technology |
示例:
标题: 耗时6个月打造功能后，我们最大的教训是“用户想要更少操作，而非更多功能”
我们打造了一个用户反复请求的功能。中途我们差点砍掉它，因为原型显得很笨重。
拯救它的关键：我们停止添加功能，开始简化步骤。最终版本的功能比原型少，但用户完成任务只需1步而非5步。
想告诉过去自己的三件事：
1. 和重度用户一起做原型，而非最活跃的用户
2. “每周迭代”会迫使你缩减功能范围 — 这是优势
3. 用户要求的东西和他们真正需要的东西是不同的
有没有人有过类似经历：砍掉功能反而让产品变得更好？3. Image Recommendations
3. 图片建议
For each platform, suggest image requirements:
| Platform | Format | Dimensions | Notes |
|---|---|---|---|
| PNG/JPG | 1200×627 | Text overlay OK, keep key message in centre | |
| PNG/JPG | 1200×630 | Minimal text (old 20% rule still affects reach) | |
| PNG/JPG | 1080×1080 | Visual-first — image must work without caption | |
| PNG/JPG | Varies | Optional — text posts often perform better |
If the skill is available, suggest using it to generate companion images with the right aspect ratios.
ai-image-generator为每个平台提供图片要求：
| 平台 | 格式 | 尺寸 | 说明 |
|---|---|---|---|
| PNG/JPG | 1200×627 | 可添加文字覆盖层，核心信息放在中间 | |
| PNG/JPG | 1200×630 | 文字尽量少（旧的20%文字规则仍会影响曝光） | |
| PNG/JPG | 1080×1080 | 视觉优先 — 图片需能脱离标题独立传达信息 | |
| PNG/JPG | 不固定 | 可选 — 纯文字帖通常表现更好 |
如果工具可用，建议用它生成符合对应宽高比的配套图片。
ai-image-generator4. Output Format
4. 输出格式
Present each post in a clearly labelled block:
═══ LINKEDIN ═══
[post content]
═══ FACEBOOK ═══
[post content]
═══ INSTAGRAM (Caption) ═══
[caption content]
═══ INSTAGRAM (First Comment — Hashtags) ═══
[hashtags]
═══ REDDIT (r/subreddit) ═══
Title: [title]
Body: [body]Save to if the user wants to keep them for scheduling.
.jez/artifacts/social-posts-[topic].md将每个帖子放在清晰标记的区块中：
═══ LINKEDIN ═══
[帖子内容]
═══ FACEBOOK ═══
[帖子内容]
═══ INSTAGRAM（标题） ═══
[标题内容]
═══ INSTAGRAM（第一条评论 — 话题标签） ═══
[话题标签]
═══ REDDIT（r/子版块） ═══
标题: [标题]
正文: [正文]如果用户需要保存用于排期，可保存至。
.jez/artifacts/social-posts-[topic].mdCampaign Mode
营销活动模式
For launches or announcements, generate a posting sequence:
| Timing | Platform | Post type |
|---|---|---|
| Day -1 | Teaser / behind-the-scenes | |
| Day 0 (morning) | All platforms | Announcement post |
| Day 0 (afternoon) | Instagram Stories | Quick video/carousel |
| Day +1 | Value-focused discussion | |
| Day +3 | Results/learnings follow-up | |
| Day +7 | Customer reaction / testimonial |
针对产品发布或公告，生成发布序列：
| 时间 | 平台 | 帖子类型 |
|---|---|---|
| 前1天 | 预热/幕后内容 | |
| 发布日（上午） | 所有平台 | 公告帖 |
| 发布日（下午） | Instagram快拍 | 短视频/轮播帖 |
| 发布后1天 | 价值导向讨论帖 | |
| 发布后3天 | 结果/收获跟进帖 | |
| 发布后7天 | 用户反馈/推荐帖 |
Quality Rules
质量规则
- Never copy-paste the same text across platforms — each platform has different conventions
- No corporate jargon — "leverage our synergies" belongs nowhere
- Front-load the value — every platform truncates. The first line must work standalone.
- Match the platform culture — LinkedIn is not Instagram is not Reddit
- Include a reason to engage — question, poll, or genuine discussion prompt
- Check character limits — LinkedIn (3,000), Facebook (63,206), Instagram caption (2,200), Reddit title (300)
- Never fake engagement — no "Drop a 🔥 if you agree" on LinkedIn, no hashtag spam on Reddit
- 绝对不要跨平台复制粘贴相同内容 — 每个平台有不同规则
- 禁用企业黑话 — “发挥协同效应”这类表述绝不允许出现
- 前置核心价值 — 所有平台都会截断内容，第一行必须能独立传达信息
- 匹配平台文化 — LinkedIn≠Instagram≠Reddit
- 加入互动理由 — 问题、投票或真诚的讨论提示
- 检查字符限制 — LinkedIn（3000）、Facebook（63206）、Instagram标题（2200）、Reddit标题（300）
- 不要伪造互动 — LinkedIn上不要用“同意就发🔥”，Reddit上不要刷话题标签