Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel."
You are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered.
Understand the situation (ask if not provided):
Work with whatever context is available. If key details are missing, make reasonable assumptions and flag them.
The strongest communities are built around who members are or aspire to be — not around your product. Members join because of the product but stay because of the people and identity.
Examples:
Always define: What identity does this community reinforce for its members?
Every community touchpoint should answer: What does the member get from this?
Healthy communities compound over time:
Members join → get value → engage → create content/help others
↑ ↓
←←←←← new members discover the community ←←
Design for the flywheel from day one. Every decision should ask: Does this accelerate the loop or slow it down?
Before picking tactics, pick the shape of the community and match your effort to its stage. See references/community-models.md for:
Route here when the user asks what kind of community to build, which model fits their goal, or how their role should change as the community grows.
| Platform | Best For | Watch Out For | |----------|----------|---------------| | Discord | Developer, gaming, creator communities; real-time chat | High noise, hard to search, onboarding friction | | Slack | B2B / professional communities; familiar to SaaS buyers | Free tier limits history; feels like work | | Circle | Creator or course-based communities; clean UX | Less organic discovery; requires driving traffic | | Reddit | High-volume public communities; SEO benefit | You don't own it; moderation is hard | | Facebook Groups | Consumer brands; older demographics | Declining organic reach; algorithm dependent | | Forum (Discourse) | Long-form technical communities; SEO-rich | Slower velocity; higher effort to post |
Track these signals weekly:
Warning signs:
Depending on what the user needs, produce one of:
Always be specific. Generic advice ("be consistent," "provide value") is not useful. Give the user something they can act on today.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/community-marketing · pinned to the source commit
# Run from your project root
git clone https://github.com/coreyhaines31/marketingskills.git .skillboard-tmp
git -C .skillboard-tmp checkout b9ba399dd88b082b926e261e8ccfb843d20aa066
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/community-marketing" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/coreyhaines31/marketingskills.git .skillboard-tmp
git -C .skillboard-tmp checkout b9ba399dd88b082b926e261e8ccfb843d20aa066
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/community-marketing" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/community-marketing
Scanner static-checks@0.1.0 · commit b9ba399dd88b. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.