community-building-playbook

Solid

Build and grow developer and user communities from scratch — covering ambassador programs, community-led growth (CLG), event operations, content strategy, and health metrics. Grounded in real playbooks from Notion, Lovable, AFFiNE, ClickUp, Asana, and Lark. Use when: building a community for an open-source project, SaaS product, or brand; recruiting and managing ambassadors or community leaders; planning community events (online/offline meetups, AMAs, hackathons); designing ambassador tier/points systems; setting community health KPIs; launching a Build-in-Public strategy; setting up Discord, Slack, or Lark communities; running developer relations (DevRel); or when the user asks about community operations, ambassador programs, CLG, user advocacy, KOC/KOL cultivation, UGC flywheels, community monetization, or any variation of "how do I grow my community".

Web & Frontend 71 stars 5 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
62
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Community Building Playbook — Developer & User Community Growth Real-world frameworks distilled from Notion, Lovable ($50M ARR in 6 months via CLG), AFFiNE (0→60K GitHub Stars), ClickUp, Asana, and Lark's global community operations. Read [`references/benchmarks.md`](references/benchmarks.md) for deep dives into each case study when you need them. --- ## The Core Principle **You cannot build a community. You can only create the conditions for one to form.** The flywheel: Great Product → Organic Love → Self-Generated Content → Community Formation → Ambassador Identification → Ambassador Enablement → More Content + Events → More Users → Repeat. Every failure to build community traces back to one of two mistakes: starting too early (pre-PMF), or treating community as a distribution channel rather than a mutual-value ecosystem. --- ## Phase 0: Are You Ready? Before any community program, run this checklist. If more than two items are unchecked, stop and build product. - [ ] Internal team uses own product daily (Notion's commercial readiness signal — they waited until 2016 to start) - [ ] Product has a usable core loop (create → use → share works smoothly) - [ ] You can share something (templates, tutorials, roadmap direction, or user cases) - [ ] Someone owns community full-time (even 20% of one person's time counts) - [ ] You can handle inbound (someone reads and responds to community posts within 24h) **The stage decision:** | Stage | Suitable? | Strategy | |-----...

Details

Author
Gingiris-1031
Repository
Gingiris-1031/gingiris-skills
Created
2 months ago
Last Updated
2 days ago
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category