| --- |
| name: gingiris-opensource |
| description: | |
| 🇺🇸 Open-Source Marketing & GitHub Stars Growth System — Decision framework for each growth stage. Pre-launch readiness → Show HN / Reddit / Product Hunt launch → 6-month growth loop. README rules, KOL outreach, dev-content matrix (dev.to / Zenn), anti-star-farming. Built from taking AFFiNE 0 → 60K stars. |
| |
| 🇨🇳 开源营销与 GitHub Star 增长系统 — 每个增长阶段的决策框架。Pre-launch 就绪 → Show HN / Reddit / Product Hunt 发布 → 6 个月增长循环。README 规则、KOL 合作、开发者内容矩阵（dev.to / Zenn）、防刷 star。提炼自 AFFiNE 0 → 60K star 实战。 |
|
|
| 🇯🇵 オープンソースマーケティング＆GitHub スター成長システム — 各成長段階の意思決定フレームワーク。Pre-launch → Show HN / Reddit / Product Hunt → 6ヶ月成長ループ。READMEルール、KOL連携、開発者コンテンツマトリックス。 |
|
|
| 🇰🇷 오픈소스 마케팅 & GitHub 스타 성장 시스템 — 각 성장 단계별 의사결정 프레임워크. 사전 출시 → Show HN / Reddit / Product Hunt → 6개월 성장 루프. README 규칙, KOL 아웃리치, 개발자 콘텐츠 매트릭스. |
|
|
| Triggers: "open source marketing" | "GitHub stars" | "star growth" | "Show HN" | "Hacker News launch" | "OSS launch" | "developer marketing" | "Reddit launch" | "dev.to" | "open source growth" | "开源营销" | "GitHub star 增长" | "开源发布" | "Show HN 怎么发" | "开发者营销" | "オープンソース" | "오픈소스 성장" |
| when_to_use: | |
| Use this skill when you need to: launch an open-source project (Show HN / Reddit / Product |
| Hunt), grow GitHub stars from 0 to 1K in 72 hours, set up README for developer conversion, |
| run KOL outreach for dev tools, or build a 6-month OSS growth loop. |
| Trigger phrases: "open source launch" | "GitHub stars" | "Show HN" | "OSS marketing" | |
| "开源发布" | "GitHub star增长" | "开源营销" | "开发者营销" | "오픈소스 성장" |
| --- |
| |
| # Open-Source Marketing — GitHub Stars Growth System |
|
|
| > 🌍 **Language / 语言**: [English](#english-version) | [中文](#中文版) |
|
|
| Stars don't come from a great repo — they come from **a great repo placed in front of the right developers, in the right order**. This is the staged decision framework used to take AFFiNE from 0 to 60K stars. |
|
|
| --- |
|
|
| ## English Version |
|
|
| ### The 3-stage framework |
|
|
| #### Stage 1 — Pre-launch (T-30 → T-0) |
| - [ ] README in **English-first**; the first screen must be understandable in <3 seconds. |
| - [ ] Demo video ≤ 60s, captioned. |
| - [ ] License chosen deliberately (MIT / Apache-2 / AGPL each carry traps). |
| - [ ] 3–5 early maintainers / contributors lined up. |
| - [ ] Community channel live (Discord or Telegram, English-first). |
|
|
| #### Stage 2 — Launch (T-0 → T+14) |
| - [ ] Product Hunt (run the dedicated launch sequence). |
| - [ ] **Hacker News Show HN** — Tuesday 9am ET, or Saturday. |
| - [ ] Reddit — pick **3** relevant subs (r/selfhosted, r/programming, one niche tech sub). |
| - [ ] Deep technical posts on dev.to / Zenn / CSDN. |
| - [ ] 3–5 KOLs to amplify (activity > follower count). |
|
|
| #### Stage 3 — Growth (T+14 → T+180) |
| - [ ] One technical blog per week. |
| - [ ] Turn GitHub Issues into content (user questions → FAQ → posts). |
| - [ ] Monthly update (mailing list + Discord). |
| - [ ] Localize for going global (Japan/Korea first). |
|
|
| ### Star Region Distribution (GitHub Trending unlock) |
|
|
| - No single country/region should exceed **20%** of your total stars. |
| - Global healthy split reference: China 19-21%, US 19-21%, rest scattered across Europe / Russia / Canada / Indonesia. |
| - Finer benchmark (from studying VSCode / Vue / AppFlowy the week before AFFiNE's launch): US 19-21%, China ~19-21%, FR+DE+IT+UK combined 10-15%; Russia and Brazil usually appear in the Top-10 countries. Week-1 stars matching this curve = healthy global cold start. |
| - Tools: **star-history.com** (trend chart) · **oss.cool / OSS Insight** (per-country breakdown, built by Chinese devs) |
| - **Launch sequence**: Week 1 → overseas-only outreach. Week 2 → domestic (Chinese) outreach. Reversing this breaks the distribution and kills Trending eligibility. |
| - AFFiNE real case: deliberately skipped WeChat Moments / Chinese community posts in week 1. |
|
|
| ### README essentials (conversion checklist) |
|
|
| - [ ] Structure: big logo → one-liner → badges → short description (reference: Dify, Lobechat, AFFiNE). |
| - [ ] **≤ 8 screens** — dev docs go in a separate link, not inline. |
| - [ ] Add a **"⭐ star reminder" GIF** (same psychology as Bilibili "like / coin / collect" prompt — users need a nudge). |
| - [ ] **Backlinks loop**: every outbound link (website, blog, docs) must have a visible GitHub link back. Don't let traffic escape with no return path. |
|
|
| ### PR article strategy |
|
|
| - Publish one authoritative article (official blog / Medium / dev.to) that fully explains the project's value. |
| - Purpose: give anyone who wants to spread your project a ready-made script. They will use it without asking. |
| - AFFiNE case: a German user independently posted to 40+ forums with no prior contact — only possible because a clear reference article existed. |
|
|
| ### Competitor follower DMs |
|
|
| - DM followers of your top competitors on Twitter/X (Notion, Miro, etc.). |
| - Real benchmark: ~hundreds of DMs → ~hundreds of star conversions. |
| - Target: users who actively complain about the competitor — they already have switching intent. |
|
|
| ### Channel order that works |
|
|
| > **English > multilingual > Chinese-only.** Unless your target *is* Chinese users, launching an English project to Chinese communities first wastes your best shot. |
|
|
| ### Anti-patterns (the things that get you un-discovered) |
|
|
| - ❌ Farming stars — GitHub detects it fast; the penalty is *disappearing from search*. |
| - ❌ Posting to Reddit once and leaving — communities resent it; high ban risk. |
| - ❌ Too many emojis / badges in the README — lowers credibility. |
| - ❌ Treating Show HN as a one-shot — engage every comment for the full day. |
|
|
| ### Day One minimum kit (1-week prep window) |
|
|
| When you only have one week to prepare (AFFiNE, open-sourced 2022-08-03, had exactly that), ship these four assets and nothing else: |
|
|
| | # | Asset | Bar | |
| |---|-------|-----| |
| | 1 | One-liner website | Big type, sparse lines: headline + subline + GitHub link on the first screen (Vercel-style OSS landing) | |
| | 2 | Illustrated README | Video/GIF > image > text; visitor gets what/why in 30 seconds, then a direct star CTA | |
| | 3 | One competitor-benchmark article | "X is an open source [top competitor] alternative" — one authoritative piece, reused across every channel | |
| | 4 | Minimal dev docs | 4 pages: who we are · features · per-OS deploy guides (macOS / Windows / Linux) · how to contribute. Rough is fine — having it beats not having it | |
|
|
| ### Cold-start 6-step SOP (validated: ≈6,000 stars in week 1) |
|
|
| 1. Study how successful OSS peers launched (AFFiNE studied AppFlowy) before doing anything. |
| 2. Ship the illustrated README (see kit above). |
| 3. Publish the "open source X alternative" positioning article. |
| 4. Submit to open-source-alternative directory sites. |
| 5. DM the Twitter/X followers of your benchmark competitor — their fans are your most precise seed pool. |
| 6. Post to Reddit and developer communities. |
|
|
| Blast steps 3-6 within a single day for concentrated volume, then let the flywheel spin. |
|
|
| ### Reverse-engineer a competitor's launch day (star-history method) |
|
|
| 1. On star-history.com / OSS Insight, find the exact open-source date of your strongest competitor. |
| 2. Google advanced search restricted to that day/week: reconstruct every post, PR and directory submission they made. |
| 3. Build the channel spreadsheet (AppFlowy case: ~40 channels — 20+ directories like opensourcealternative.to, Medium / dev.to, dev forums, Reddit), tagged free/paid. |
| 4. Pick competitors that launched in the last 2-3 years and are within reach — don't dissect an 8-year-old giant. |
|
|
| Expectation setting: copying the SOP does not guarantee 6,000 stars in a week, but 1,000-3,000 stars in 3 months is realistic. |
|
|
| ### Open source as fundraising leverage (AFFiNE data chain) |
|
|
| | Before open source | After open source (2022-08-03) | |
| |---|---| |
| | Angel round: ~400 investor meetings over ~12 months (self-reported) | Week 1: ≈6,000 stars, 80% from overseas | |
| | | Day 43: 10,000 stars | |
| | | ~1 month post-launch: $8M Pre-A locked | |
| | | 24 months: 60K+ stars | |
|
|
| - Investors buy **star growth rate**, not the absolute count — velocity is the signal. |
| - Investors may run crawlers during due diligence to verify stars aren't botted; a clean history is itself an asset. |
|
|
| ### Monetization pricing test (before the paid product exists) |
|
|
| - Put up a pricing page even before the paid tier is built — tiers can stay vague. Give each tier a "contact us" + typeform (tier + question + contact info). |
| - AFFiNE result: dozens of pricing inquiries within 2 weeks; the question shifted from "is this free?" to "how much will it cost?". Interest split ≈ 70% community free / 20% personal / 10% team. |
| - Tell users early that a paid model exists — the sooner you say it, the sooner the mental model forms. Actively fight the "open source = free" stereotype. |
| - As strategy shifts toward general users, progressively shrink the "open source / privacy-first" wording on the website and retire "always free" from the tagline (AFFiNE dropped it in 2023-02). |
|
|
| ### What to do next |
|
|
| - Stage 1 done → run the Product Hunt launch sequence. |
| - Show HN succeeds → add SEO monitoring on "`<project> github`". |
| - Need a content engine → move to the blog-writing workflow. |
| - Spotted a competitor's new play → run a competitor teardown. |
|
|
| --- |
|
|
| ## 中文版 |
|
|
| ### 3 阶段框架 |
|
|
| #### 阶段 1 — Pre-launch（T-30 → T-0） |
| - [ ] README **英文主**，首屏 <3 秒读懂。 |
| - [ ] Demo video ≤ 60s，带字幕。 |
| - [ ] License 选对（MIT / Apache-2 / AGPL 各有陷阱）。 |
| - [ ] 3–5 个早鸟 maintainer / contributor。 |
| - [ ] 社群频道就位（Discord 或 Telegram，英文为主）。 |
|
|
| #### 阶段 2 — Launch（T-0 → T+14） |
| - [ ] Product Hunt（走统一发布流程）。 |
| - [ ] **Hacker News Show HN** — 周二美东 9am 或周六。 |
| - [ ] Reddit — 选 **3** 个相关 sub（r/selfhosted、r/programming、细分技术 sub）。 |
| - [ ] dev.to / Zenn / CSDN 发技术深度文。 |
| - [ ] 找 3–5 个 KOL 转（活跃度 > follower 数）。 |
|
|
| #### 阶段 3 — Growth（T+14 → T+180） |
| - [ ] 每周 1 篇技术 blog。 |
| - [ ] GitHub Issues → 内容素材（用户问题变 FAQ）。 |
| - [ ] 每月 1 次 update（邮件列表 + Discord）。 |
| - [ ] 出海本地化（日韩先）。 |
|
|
| ### Star 地区分布 & 发布时序 |
|
|
| - 同一国家/地区 star 占比不超过 **20%**，否则难上 Trending。 |
| - 健康分布参考：中国19-21%、美国19-21%，其余分散欧洲/俄罗斯/加拿大/印尼。 |
| - 更细基准（AFFiNE 开源前一周研究 VSCode / Vue / AppFlowy 得出）：美国 19-21%、中国 ~19-21%、法德意英合计 10-15%，Top10 国家通常有俄罗斯和巴西。第一周 star 分布吻合此曲线 = 冷启动全球化健康。 |
| - 工具：**star-history.com**（涨幅趋势）· **OSS Insight**（国家分布，国人开发） |
| - **发布时序**：第一周只做海外宣发，第二周才做国内。顺序反了会破坏分布比例。 |
| - AFFiNE 真实案例：开源第一周故意不发朋友圈、不进国内社群。 |
|
|
| ### README 优化要点 |
|
|
| - [ ] 结构：大logo + 一句话介绍 + badges + 简短介绍（参考 Dify / Lobechat / AFFiNE） |
| - [ ] **不超过 8 屏**，开发者文档单独一个链接，不塞进 README |
| - [ ] 加**提醒点 star 的小动图**（类比B站UP主「一键三连」——用户需要被提醒） |
| - [ ] **backlinks 循环**：所有跳出去的链接（官网/博客/文档站）必须能跳回 GitHub，流量不能有去无回 |
|
|
| ### PR 文章策略 |
|
|
| - 准备一篇阐述项目优势的完整文章（官网 Blog / Medium / dev.to） |
| - 目的：给所有想帮你传播的人一把枪，他们可以直接引用，不需要自己想怎么介绍 |
| - AFFiNE 案例：一个德国用户发了 40 多个论坛，没打招呼就发了——能发出去，是因为有参考文章 |
|
|
| ### 竞品 follower 私信 |
|
|
| - 给竞品（Notion / Miro 等）的 Twitter follower 发私信 |
| - 实战数据：几百条私信 → 几百个 star 转化 |
| - 优先找「吐槽竞品」的用户，他们已经有切换意愿 |
|
|
| ### 渠道顺序 |
|
|
| > **英文 > 多语言 > 纯中文。** 除非目标就是中文用户，否则把英文项目先发中文社群是浪费最好的一次机会。 |
|
|
| ### 反模式 |
|
|
| - ❌ 刷 star（GitHub 很快检测，后果是搜不到）。 |
| - ❌ Reddit 只发一次就跑（社群反感，易被 ban）。 |
| - ❌ README 太多 emoji / badge（降低可信度）。 |
| - ❌ 把 Show HN 当一锤子买卖（要回一整天评论）。 |
|
|
| ### 2026 实验记录与生态分发 |
|
|
| - 每次渠道动作都写一行实验记录：`日期 / 假设 / 渠道 / 素材 / UTM / 24h结果 / 7d结果 / 下一步`。Star 只作领先指标，同时看安装、首次成功运行、回访和付费意向。 |
| - README、Demo 视频、最短可运行路径是同一条激活链；任何一步超过 3 分钟，都先修激活再放大流量。 |
| - 把项目提交到真实相关的 Awesome Lists、包管理器、模板市场和上下游集成目录；逐站遵守投稿规则，不批量灌水、不买链接。 |
| - 案例数字必须标注日期、样本范围和 `self-reported` / 可验证来源，避免把历史平台规律写成永久算法事实。 |
|
|
| ### 开源 Day One 四件套（一周准备期最小集） |
|
|
| 只有一周准备时间时（AFFiNE 2022-08-03 开源，就是这个节奏），只做这四件： |
|
|
| | # | 资产 | 标准 | |
| |---|------|------| |
| | 1 | 一句话官网 | 字大行稀：首屏只有主标题+副标题+GitHub 链接（对标 Vercel 类开源官网） | |
| | 2 | 图文并茂 README | 能上视频/GIF 就上，退而求其次上图；30 秒内让人 get 价值，并直接引导点 star | |
| | 3 | 一篇对标竞品文章 | "X is an open source [头部竞品] alternative"——一篇权威稿全渠道复用 | |
| | 4 | 最小开发者文档集 | 4 篇：我们是谁 · 功能介绍 · 分系统部署（macOS / Windows / Linux）· 如何参与贡献。粗糙没关系，有比没有好 | |
|
|
| ### 开源冷启动 6 步 SOP（实证：第一周 ≈6,000 star） |
|
|
| 1. 先研究成功开源前辈怎么发布的（AFFiNE 学的是 AppFlowy），再动手。 |
| 2. 备好图文并茂 README（见上面四件套）。 |
| 3. 发一篇「我是 XXX 的开源替代」定位文章。 |
| 4. 提交 open-source-alternative 类导航站。 |
| 5. 私信对标竞品的 Twitter/X 粉丝——竞品粉丝就是最精准的种子池。 |
| 6. Reddit 和开发者社区发帖。 |
|
|
| 第 3-6 步一天之内集中铺完，打出声量后等飞轮。 |
|
|
| ### star-history 逆向工程竞品开源日 |
|
|
| 1. 在 star-history.com / OSS Insight 查最强竞品的开源日期。 |
| 2. Google 高级搜索限定那一天/那一周，还原竞品当天发的所有帖子、PR、导航站提交。 |
| 3. 拉渠道大表（AppFlowy 案例约 40 个渠道：20+ 导航站如 opensourcealternative.to、Medium / dev.to、开发者论坛、Reddit），标注免费/付费。 |
| 4. 选近 2-3 年发布、体量"勾勾手够得着"的竞品，别拆 8 年前的老巨头。 |
|
|
| 预期管理：照抄 SOP 不保证一周 6,000 star，但 3 个月 1,000-3,000 star 相对容易。 |
|
|
| ### 开源撬动融资（AFFiNE 数据链） |
|
|
| | 开源前 | 开源后（2022-08-03） | |
| |---|---| |
| | 天使轮：见了 ~400 个投资人、耗时约 12 个月（口述口径） | 第一周：≈6,000 star，80% 来自海外 | |
| | | 第 43 天：破 1 万 star | |
| | | 开源后约 1 个月：锁定 $8M Pre-A | |
| | | 24 个月：60K+ star | |
|
|
| - 投资人真正买单的是 **star 增速**而非绝对值——速度才是信号。 |
| - 投资人 DD 时可能写爬虫验证 star 是否刷量，干净的历史本身就是资产。 |
|
|
| ### 商业化 pricing test（付费版还没做出来就能测） |
|
|
| - 商业版没做出来也先挂 pricing 页——档位可以写得模糊，每档配 contact us + typeform（选档位+问题+联系方式）。 |
| - AFFiNE 结果：两周收到几十个问价；咨询口径从「这免费吗」变成「大概多少钱」。意向比例 ≈ 70% community free / 20% 个人版 / 10% team 版。 |
| - 及早告诉用户产品有付费模式——越早说，用户越早建立付费认知；主动对抗「open source = free」刻板印象。 |
| - 战略转向 general user 后，官网上 "open source / privacy-first" 字样逐步变小，tagline 去掉 "always free"（AFFiNE 于 2023-02 改掉）。 |
|
|
| --- |
|
|
| *By Iris (生姜 Iris) · ex-COO @ AFFiNE (0 → 60k★) · Install: `npx skills add Gingiris-1031/gingiris-opensource`* |
|
|
