| name | community-builder |
| description | Designs community building strategies for startups. Covers platform
selection, onboarding flows, engagement mechanics, moderation
guidelines, and growth playbooks for Discord/Slack/forum communities.
|
| metadata | {"version":"1.0.0","category":"marketing","domain":"community"} |
| triggers | ["community","커뮤니티","discord","slack community"] |
Community Builder - Community Strategy & Setup
Overview
Builds communities that become your startup's unfair advantage. A strong community provides feedback, support, word-of-mouth, and a moat competitors can't copy.
1. When to Apply
| Trigger | Behavior |
|---|
| Starting a community | Full setup guide |
| "community", "discord" | Platform-specific setup |
| Community engagement dropping | Re-engagement playbook |
2. Platform Selection
| Platform | Best For | Cost | Setup |
|---|
| Discord | Dev tools, gaming, tech community | Free | Fast |
| Slack | B2B, professional communities | Free (limited) | Fast |
| GitHub Discussions | Open source projects | Free | Minimal |
| Circle/Bettermode | Premium communities, courses | $$ | Medium |
| Reddit (subreddit) | Public discovery, SEO | Free | Minimal |
3. Community Setup Template
Discord Server Structure
📢 announcements (read-only, updates)
👋 introductions (new members say hi)
💬 general (main chat)
❓ help-and-support (product questions)
💡 feature-requests (product ideas)
🐛 bug-reports (issue reporting)
🏗️ show-and-tell (users share what they built)
📚 resources (guides, tutorials)
🎉 wins (celebrate user achievements)
──── Team Only ────
🔒 team-internal (private team chat)
🔒 feedback-review (review user feedback)
Community Rules
## Community Guidelines
1. **Be respectful** — Treat everyone with kindness
2. **Stay on topic** — Use the right channels
3. **No spam** — Self-promotion in designated threads only
4. **Search first** — Check if your question was already answered
5. **Share knowledge** — Help others when you can
6. **Report issues** — Flag violations to moderators
4. Growth Phases
| Phase | Size | Focus | Actions |
|---|
| Seed | 0-100 | Quality over quantity | Personal invites, 1:1 conversations |
| Growth | 100-1K | Engagement habits | Regular content, AMAs, challenges |
| Scale | 1K-10K | Self-sustaining | Community leaders, user-generated content |
| Mature | 10K+ | Governance | Moderation team, sub-communities |
Seed Phase Playbook (First 100 Members)
1. Invite your first 10 users personally
2. Post a welcome message with YOUR story
3. Ask questions daily (seed conversations)
4. Respond to every message within 4 hours
5. Highlight early members publicly
6. Share product updates first in community
7. Host a weekly AMA or office hours
5. Engagement Mechanics
| Mechanism | Description | Effort |
|---|
| Welcome flow | Auto-welcome + intro prompt | Low |
| Weekly thread | "What are you working on?" | Low |
| Office hours | Live Q&A with founders | Medium |
| Challenges | Build/create something with product | Medium |
| Spotlight | Feature community members | Low |
| Early access | Beta features for community | Medium |
| Community roles | Power users become moderators | Low |
6. Tool Coordination
| Tool | Purpose |
|---|
| Write | Generate community setup docs, guidelines |
| Read | Reference existing community strategy |
7. Boundaries
Will:
- Design community structure and strategy
- Create channel layouts and moderation guidelines
- Provide growth phase playbooks
- Suggest engagement mechanics
Will Not:
- Create Discord/Slack servers (provide the blueprint)
- Moderate communities
- Generate daily content for community
- Manage community member relationships
