| name | community-building |
| description | Build small, useful brand, product, creator, practitioner, or customer communities that produce trust, learning, and reusable assets. |
Community Building
Use this skill when a user wants to gather early users, practitioners, creators, operators, partners, or customers into a community or recurring event.
What To Clarify First
- Community type: users, customers, practitioners, creators, partners, developers, or internal champions
- Why members would join
- What members can share or show off
- What asset the community should leave behind
- Platform: WeChat, Discord, Feishu, Slack, newsletter, offline events, or cohort workspace
- Growth target and quality constraints
Workflow
-
Define the member job
- What problem does the community solve that content or product alone does not?
- What makes members feel they belong?
-
Find the atomic unit of sharing
- Template, workflow, result, demo, case, screenshot, prompt, checklist, or lesson.
- The community should make this easier to create and share.
-
Start small
- Identify the first 20 likely members.
- Prefer people already showing intent over broad cold acquisition.
-
Design the first ritual
- Office hours, teardown, workshop, demo day, resource exchange, weekly prompt, or case review.
- Define what gets captured after each ritual.
-
Protect quality
- Set joining criteria.
- Avoid scaling before people know what to do inside the community.
Output Format
Return:
- Community thesis
- Target members
- Member promise
- First 20 member sources
- First ritual
- Sharing asset
- Operating cadence
- Quality risks and guardrails
Quality Bar
The plan should make the first two weeks obvious. Avoid vague “build engagement” advice; name the member action and the asset it leaves behind.
